For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

If you use vanity name servers (also called branded name servers) with DigitalOcean’s authoritative DNS service, your domains may fail to resolve if the name servers’ A, AAAA, or glue records point to incorrect IP addresses.

This issue doesn’t affect domains that don’t use vanity name servers with DigitalOcean’s authoritative DNS service. To verify your configuration, check your domain registrar and confirm that your domain’s NS records point to ns1.digitalocean.com, ns2.digitalocean.com, and ns3.digitalocean.com.

Check Your Vanity Name Server Configuration

If you continue to use vanity or branded name servers, confirm that the following records point at DigitalOcean’s current name server IPs:

• Any A or AAAA records for the vanity name server hostnames. Configure these records using the DigitalOcean Control Panel, API, or doctl 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.

The A and AAAA records in DigitalOcean DNS and the glue records at your domain registrar must point to the current IP addresses of DigitalOcean’s authoritative name servers:

Related Topics

How do I fix the DNS error "Primary Name Server Not Listed at Parent"?

Update your registrar to use DigitalOcean’s name servers.

Why does my domain fail to resolve?

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

Your load balancer may be down or not directing traffic to the target Droplet.