# Why aren't my vanity DNS name servers resolving?

We have changed the IP addresses of our authoritative DNS service. Customers using *vanity name servers* (also known as *branded name servers*) must update their DNS configuration to reflect these changes. If no action is taken, domains delegated to DigitalOcean’s authoritative DNS service may not resolve properly beginning 9 January, 2025.

**Note**: The use of vanity/branded name servers is not officially supported by DigitalOcean, and can lead to unexpected problems we can not diagnose. We highly encourage delegating your domains to use our name server domains: `ns1.digitalocean.com`, `ns2.digitalocean.com`, and `ns3.digitalocean.com`.

If your domains are not using vanity name servers based on DigitalOcean’s authoritative DNS service, this change does not affect you. To confirm you are not using vanity name servers, check the configuration at your domain registrar and verify that your domain’s `NS` entries are pointing to `ns1.digitalocean.com`, `ns2.digitalocean.com`, and `ns3.digitalocean.com`.

## How to Update Your Domain Configuration

Customers who are using vanity or branded name servers for DNS resolution must update the following DNS configurations:

- Any `A` or `AAAA` records that point to the old name server IPs (listed in the table below). Configure these records using the DigitalOcean [Control Panel](https://cloud.digitalocean.com/networking/domains), [API](https://docs.digitalocean.com/reference/api/digitalocean/index.html.md#tag/Domains), or [`doctl`](https://docs.digitalocean.com/reference/doctl/reference/compute/domain/index.html.md) CLI tool.
- Any *glue records* created with your domain registrar. Glue records are records that are configured with your registrar to delegate domain resolution. Glue records can sometimes be listed as **Registered Name Servers** or **Name Server IPs** in your registrar’s configuration interface.

Failure to update **both** the `A` and `AAAA` records on DigitalOcean **and** glue records created with your registrar could lead to DNS resolution problems for your domain.

Update to the new name server IPs as soon as possible, as service to the old IPs officially ended on 17 December, 2024. The new IPs are:

| Name Server | | Old IP | New IP |
|---|---|---|---|
| ns1.digitalocean.com | IPv4 | 173.245.58.51 | 172.64.52.210 |
| | IPv6 | 2400:cb00:2049:1::adf5:3a33 | 2606:4700:52::ac40:34d2 |
| ns2.digitalocean.com | IPv4 | 173.245.59.41 | 172.64.53.21 |
| | IPv6 | 2400:cb00:2049:1::adf5:3b29 | 2606:4700:5a::ac40:3515 |
| ns3.digitalocean.com | IPv4 | 198.41.222.173 | 172.64.49.209 |
| | IPv6 | 2400:cb00:2049:1::c629:dead | 2606:4700:52::ac40:31d1 |

## Related Topics

[How do I fix the DNS error "Primary Name Server Not Listed at Parent"?](https://docs.digitalocean.com/support/how-do-i-fix-the-dns-error-primary-name-server-not-listed-at-parent/index.html.md): Update your registrar to use DigitalOcean’s name servers.

[Why does my domain fail to resolve?](https://docs.digitalocean.com/support/why-does-my-domain-fail-to-resolve/index.html.md): A domain could fail to resolve because the name server changes did not completely propagate, `DNSSEC` or the domain registrar needs verification, the DigitalOcean name servers are not configured at your registrar, or there are different name server providers active.

[I can't reach a Droplet through my DigitalOcean Load Balancer](https://docs.digitalocean.com/support/i-cant-reach-a-droplet-through-my-digitalocean-load-balancer/index.html.md): Your load balancer may be down or not directing traffic to the target Droplet.