DNS configuration - domain won't resolve

2 posts / 0 new
Last post
#1 Sun, 05/28/2017 - 11:35
Peter Parker

DNS configuration - domain won't resolve

Hi all, I've installed Webmin and Virtualmin on a new CentOS 7 server to migrate sites from a dedicated cPanel server. The installation went smoothly, all services are running correctly and passing the 'Checking Configuration' script without error.

My server's sanitized hostname is 'server.mydomain.com' and I'm able to connect to Webmin by https://{ip-address}:10000 but not via http://server.mydomain.com:10000 as it doesn't resolve.

I've setup two nameservers at the registrar as server.mydomain.com, ns2.mydomain.com

If I ping the above nameservers the correct IP addresses assigned at the registrar are resolved but there's no reply from the server.

$ ping server.mydomain.com
PING server.mydomain.com (66.70.0.0) 56(84) bytes of data.
^C
--- server.mydomain.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

For testing purposes I disabled the firewall so there's nothing dropping or rejecting ICMP, but there's still no response at all.

Pinging the domain itself doesn't even resolve to an IP address:

$ ping mydomain.com      
ping: mydomain.com: Name or service not known

via http:

mydomain.com’s server DNS address could not be found. ERR_NAME_NOT_RESOLVED

DNS Records:

$ttl 3600
mydomain.com. IN SOA server.mydomain.com. admin.gmail.com. (
1495730669
10800
3600
604800
38400 )
@ IN NS server.mydomain.com.
@ IN NS ns2.mydomain.com.
mydomain.com. IN A 158.69.0.0
www.mydomain.com. IN A 158.69.0.0
ftp.mydomain.com. IN A 158.69.0.0
m.mydomain.com. IN A 158.69.0.0
localhost.mydomain.com. IN A 127.0.0.1
webmail.mydomain.com. IN A 158.69.0.0
admin.mydomain.com. IN A 158.69.0.0
mail.mydomain.com. IN A 158.69.0.0
mail.mydomain.com. IN MX 5 mydomain.com.
mydomain.com. IN TXT "v=spf1 a mx a:mydomain.com ip4:158.69.0.0 ip6:2607:5300:0:0:: ?all"
server 3600 IN A 66.70.0.0
ns2     3600    IN      A       66.70.0.1

Thanks for any help.

Mon, 05/29/2017 - 18:43
Joe
Joe's picture

Are you sure your glue records at the registrar are correct and working?

You can usually see that on the command line with the whois command or something like "dig NS virtualmin.com @a.gtld-servers.net", where "virtualmin.com" would be replaced by your domain, and a.gtld-servers.net would be any top-level domain name server for your TLD--the one I've used is for .com...if your domain is something else, you'll need to first find the TLD name servers..."dig NS org" would find the TLD servers for .org domains.

--

Check out the forum guidelines!

Topic locked