---
name: vpc-vpe-ts-cannot-access-url
title: Why can't I can access a service by using the service's URL?
description: You are supposed to be able to access a service by using the reserved IP or service's URL. If you can't access a service by using the URL, you might need to force the DHCP client to renew its lease.
last-updated: 2023-01-27
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vpc?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why can't I can access a service by using the service's URL?
{: #troubleshoot-cannot-access-url}
{: troubleshoot}
{: support}

You are supposed to be able to access a service by using the reserved IP or service's URL. If you can't access a service by using the URL, you might need to force the DHCP client to renew its lease.
{: shortdesc}

Cannot use the service's URL to access the service.
{: tsSymptoms}

The DNS service was not able to change the default DNS server for the virtual server instance that's trying to access the service.
{: tsCauses}

To correct this issue, follow steps similar to the following Ubuntu commands:
{: tsResolve}

1. In the virtual server instance, check the last lease in `/var/lib/dhcp/dhclient.leases`. The entry for DNS servers is to read option `domain-name-servers 161.26.0.7,161.26.0.8`, not `161.26.0.10,161.26.0.11`.
1. If this entry is not updated, run `/sbin/dhclient` to force the DHCP client update.