Skip to content

Check DNS when a domain points to the wrong server

Check A, AAAA, nameserver delegation, and cached answers before changing the server.

Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page

Start with the intended address

Compare the service IP with your DNS provider's records. Add an A record for IPv4. Add an AAAA record only when your server has working IPv6 and the application listens on it. An old AAAA record can make some visitors reach the wrong destination.

Read-only check

From your Windows computer, replace the example hostname:

Resolve-DnsName app.example.com -Type A
Resolve-DnsName app.example.com -Type AAAA

No AAAA answer is normal when IPv6 is not configured. DNS changes can remain cached until the previous TTL expires; repeatedly editing records does not clear other people's caches.

Check the right DNS zone

Your domain must use the nameservers for the zone you edited. If a proxy/CDN is enabled, a public answer may be the proxy address instead of your origin. Check the configured origin separately. Do not change nameservers until you have copied required mail and other records.

Was this not enough?Include the service number, exact error, and time of the problem. Never send a password or private key.
Contact support