Error: Your hostname could not be resolved to an IP address
If the DNS for your hostname is not set up correctly, you may receive an email saying something similar to this:
Most of the time, this error email is triggered by private name servers not being set up correctly. It could also mean there are missing, corrupted or improperly formatted DNS records.
Private Name Servers
If you are using private name servers (optional on Reseller and required on VPS and Ddedicated Servers), then please check the following items to ensure accuracy:
- Did you register your private name servers with your registrar with the correct IP addresses?
- Is there an A record for each of your private name servers?
- Are the correct nameservers listed in the DNS zone for the domain using them? (DNS Glue)
Generic Name Servers and A records
If you are not using private name servers, or your private name servers are set up correctly, then you may be missing the A record for your hostname. To check:
- Log into WHM.
- Click on the DNS Functions icon or navigate to the DNS Functions section in the sidebar.
- Click on Add an A Entry for your Hostname.
- Check to see if an A record exists:
- If an A record exists, it will be shown there. Make sure it shows the correct IP address (contact support if you are not sure).
- If no A record exists, then use the Add Entry button to add the IP. Make sure the correct IP is listed there before continuing. This will add the missing A record.
On a Dedicated Server or VPS, you would also want to make sure the hostname exists in /etc/hosts as well.