Skip to main content

How to Verify the Server Hostname, Reverse DNS, and Nameserver Records

Verify the server's hostname, Reverse DNS (rDNS), and nameserver records to ensure proper mail delivery and network connectivity. This process is performed by a Server Administrator within the WHM interface and via the command line.

Verify the server's hostname, Reverse DNS (rDNS), and nameserver records to ensure proper mail delivery and network connectivity. This process is performed by a Server Administrator within the WHM interface and via the command line.

Before you begin

You will need:

  • Root access to the WHM interface.

  • The server's primary IPv4 address.

  • Access to a terminal (SSH) to perform DNS lookups.

Verify the Server Hostname

The server hostname must be a Fully Qualified Domain Name (FQDN) that matches the records in your DNS zone.

  1. Log in to WHM.

  2. Navigate to Server Configuration > Basic Hostname Setup.

  3. Verify that the Hostname field contains the correct FQDN (e.g., server.example.com).

  4. Verify that the Hostname matches the primary entry in your DNS zone.

Verify Reverse DNS (rDNS)

Reverse DNS ensures that the IP address of your server resolves back to your server's hostname. This is critical for preventing your outgoing emails from being flagged as spam.

  1. Open a terminal and connect to your server via SSH.

  2. Run the following command, replacing 1.2.3.4 with your server's actual IP address:

    host 1.2.3.4

  3. Confirm that the output displays your server's FQDN (e.g., 1.2.3.4.1.2.3.4.reverse.example.com or 1.2.3.4.example.com).

Note: If the result does not match your server's FQDN, you must update the Reverse DNS record with your IP provider.

Verify Nameserver Records

Verify that your nameservers are correctly pointing to your server and that the records are correctly propagated.

  1. From the terminal, use the dig command to check the nameservers for your domain:

    dig +short NS example.com

  2. Verify that the output lists the correct nameservers (e.g., ns1.example.com and ns2.example.com).

  3. Verify that the nameservers themselves resolve to the correct server IP addresses:

    dig +short ns1.example.com

Confirm the result

  • The Basic Hostname Setup in WHM displays the correct FQDN.

  • The host command for your IP address returns your server's FQDN.

  • The dig command for your domain returns the correct nameservers.

Limitations

  • Reverse DNS (rDNS) updates may take some time to propagate depending on your IP provider's infrastructure.

  • DNS propagation times vary by registrar and DNS provider; changes may not be visible globally immediately.

Did this answer your question?