If a DNS zone does not resolve from the authoritative nameserver, it typically indicates a configuration error in the DNS records, a propagation delay, or a local caching issue. This guide helps a WHM Server Administrator identify and resolve why a specific zone is not resolving correctly from the server's own authoritative nameservers.
Before you begin
You will need:
Root access to the server via WHM.
The specific domain name and the nameservers assigned to that domain.
Access to a terminal (SSH) to run diagnostic commands.
Check the DNS zone configuration in WHM
Verify that the records within the zone are correctly configured in the WHM interface.
Log in to WHM.
Navigate to DNS Functions > DNS Zone Manager.
Select the domain from the list and click Edit DNS Zone.
Verify the following:
A Records: Ensure the domain and any subdomains (e.g.,
www) point to the correct IP addresses.NS Records: Ensure the nameservers listed are the correct authoritative servers for the domain.
SOA Record: Ensure the primary nameserver listed in the SOA record is correct.
If any records are incorrect, update them and click Save.
Verify the local resolution via the command line
Use the dig command to determine where the resolution is failing.
Connect to your server via SSH.
Run the following command to check the A record:
dig @nameserver.example.com example.com(Replacenameserver.example.comwith the actual authoritative nameserver andexample.comwith the target domain.)Analyze the ANSWER SECTION:
If the section is empty, the zone is not configured correctly or the nameserver is not looking at the correct zone.
If the record appears but is incorrect, the zone file has been updated but may not have been reloaded.
Run a reverse lookup to verify the IP:
dig -x 123.123.123.123(Replace123.123.123.123with the server's IP address.)
Check for local caching and propagation
Sometimes the record is correct, but the local resolver or a local cache is providing stale information.
Flush the local DNS cache on the server (if applicable):
systemctl restart nscd(ornscddepending on your OS).Check the TTL (Time to Live) of the record:
dig example.comIf the TTL is high and the record is incorrect, the change may not have propagated yet. You must wait for the TTL to expire before the new record becomes active.
Verify the nameserver's "Glue" records
If the nameservers themselves are not resolving, the issue may be with the registrar's glue records.
Check the status of the nameservers using
dig:dig -x nameserver.example.comIf the nameserver does not resolve to the correct IP, contact the domain registrar to ensure the "Glue" records (IP addresses for the nameservers) are correctly set in their system.
Confirm the zone is active in the local zone file
Ensure the zone file is physically present and recognized by the BIND (or other DNS software) service.
Navigate to the zone directory (typically
/var/named/or/etc/bind/).Locate the zone file for the domain.
Verify that the file exists and contains the correct records.
If the file is missing or outdated, you may need to rebuild the zone or restart the DNS service:
systemctl restart named
Confirm the result
The resolution is successful when:
The
digcommand against the authoritative nameserver returns the correct IP address in the ANSWER SECTION.The
dig -xcommand returns the correct domain name for the server's IP.The domain resolves correctly from external testing tools.
If the record is correct but still doesn't resolve
If the records are correct in WHM and the dig command against the authoritative server returns the correct IP, but the site is still unreachable:
Check the Firewall: Ensure the server is not blocking port 53 (UDP/TCP) for DNS traffic.
Check the Web Server: Ensure the web server (Apache or Nginx) is running and listening on the correct IP.
Check the IP Reputation: Ensure the server's IP address has not been blacklisted or blocked by a firewall.
Limitations
This procedure does not address issues caused by incorrect records at the domain registrar level (e.g., incorrect Glue records).
This procedure does not account for DNS propagation delays; if a change was made very recently, it may take time to reflect globally.
This does not resolve issues related to incorrect web server configurations or local ISP caching.
