Some domains don't resolve, most do

modem

Verified User
Joined
Apr 7, 2004
Messages
364
Hello all,

This issue just appeared randomly in the last 2 days and I can not figure out what is causing it. No new software/updates have been performed on the server in over 2 months. This issue just came out of no where and I have not been able to resolve it.

The issue is that one of my customers initially reported email was not working and was giving me the error message that the server could not be found. When I tried to ping their email server sure enough pings from their workstations, my office, etc show (unknown host).

I logged onto the server via SSH and also through Webmin and pinged the domain mail.preferredchoicemtg.com which was hosted right on that very same server and even the servers console reported that the host was an unknown host. So I immediately tried pinging mail.preferredchoicemtg.com, www.preferredchoicemtg.com, preferredchoicemtg.com, and every other option I could as listed in the DNS. All of which reported "unknown host". I received this when pinging from the end users machine, from my machine and when logged onto the server via SSH. The very odd thing is other domains on that same server ping just fine and respond just fine.

I checked /etc/named.conf and it appeared to be just fine indicating that the preferredchoicemtg.com.db file was located in /var/named/. So I went to that directory to open and check the file and it appears to be OK in that it's correctly setup.

Does anyone have any idea what is causing this? I also checked the DNS servers I'm using for forwarding, for what is listed in the configuration file, and for the ncsd service on the server and everything seems to be fine with that. I have no idea how to resolve this when it doesn't appear anything is broken and nothing has been installed recently.

What makes this weird is that the preferredchoicemtg.com domain is completely well within it's expiration of 2009. This domain and another domain, symgara.com are the only two that are behaving like this. Every other domain hosted on my server is working just fine. All domains are registered through Enom using my dns servers. So there is nothing that I can think of that would make these two domains just stop responding to pings tracerts, or anything else.

Help!!
 
Make sure the zone is referenced in named.conf . Check your zone file for consistancy.
 
I checked /var/named.conf and this entry looks correct:

zone "preferredchoicemtg.com" { type master; file "/var/named/preferredchoicemtg.com.db"; };


Thus I went to the actual zone file and checked it and it apears to be OK. It's contents are:

***********************************************
$TTL 14400
@ IN SOA ns1.modemnet-dns.com. root.preferredchoicemtg.com. (
2008090300
14400
3600
1209600
86400 )

preferredchoicemtg.com. 14400 IN NS ns1.modemnet-dns.com.
preferredchoicemtg.com. 14400 IN NS ns2.modemnet-dns.com.

ftp 14400 IN A 69.64.171.88
localhost 14400 IN A 127.0.0.1
mail 14400 IN A 69.64.171.88
mtbg 14400 IN A 70.88.229.213
pop 14400 IN A 69.64.171.88
winc 14400 IN A 70.88.188.197

preferredchoicemtg.com. 14400 IN MX 10 mail

preferredchoicemtg.com. 14400 IN CNAME olympiawest.com.
www 14400 IN CNAME olympiawest.com.


preferredchoicemtg.com. 14400 IN TXT "v=spf1 a mx ip4:69.64.171.88 ?all"
***********************************************


I'm still not sure what is causing this. Everything with the zone file appears to be fine.
 
Last edited:
type: service named restart

Then look at the bottom of /var/log/messages for errors.

After looking at your zone file I bet it is the cname entrys causing it to not load right.
 
And if you can, you probably shouldn't, at least not if you're going to use subdomains (only) in the rest of the records. It appears that modem has removed the cname records and replaced them with A records. It appears the zone now works :).

Jeff
 
Jeff you are indeed correct. It was the CNAME record that threw things off big time. The owner of the domain last week wanted me to forward the 'webpage' to another domain after their companies are merging. I may the CNAME change at the office mixing it up with domain forwarding. I've instructed them to make sure the new company has t;hings setup on their server to accept requests for the virtual domain of preferredchoicemtg.com to send it to their site.
 
Back
Top