Thread: Domain name resolve problems in WHM

Make sure you have /etc/resolv.conf configured correctly?

check the DNS records once at centralops.net

Hi, Check this command on your server. dig @IPAddress www.domain.com If it resolves then DNS is fine on your server.

Quote: Make sure you have /etc/resolv.conf configured correctly? Yes, it is correctly configured. Quote: check the DNS records once at centralops.net DNS records are ok. Quote: Hi, Check this command on your server. dig @IPAddress www.domain.com...

As mentioned, make sure you have the proper DNS servers in /etc/resolv.conf - check with your server provider to make sure the proper IPs are in there....just have a hunch for some reason, even though you've noted that resolv.conf is correct. Adding 'options rotate' to the resolver config wouldn't hurt either, if it's missing. You could also see if ipchains or another firewall are blocking a ...

Try dig +trace somedomain.com (for a domain that resides on your server). Please remember to clear DNS cache before doing so.

Check the DNS report at: http://intodns.com/ If you don't see the name server IPs OR different name servers, then something is definitely wrong somewhere.

Quote: Originally Posted by madaboutlinux Check the DNS report at: http://intodns.com/ This. Intermittent lookup failures are usually caused by mismatched glue. And dig, dig @IP or dig +trace will not show the error - to see it with dig you need to check the nameserver IP address - "dig @yourIP ns.example.com...

www.network-tools.com is another nifty tool when it comes to checking zones and how they're setup. You can check your domain/IP against the utility and see if you can find a mismatch, as noted above.

I have found that my name servers does not resolves? Can anyone know why they don't?