New Domains won't resolve for clients

[modem]

Hello all,

I have a weird problem that I have recently discovered after new clients sign up for service and get a new domain hosted on my server. Their domains simply will *not* resolve to the IP and trying to ping their domain name results in messages like: "Ping request could not find <domainname.com>...". I go back and check that all of the settings inside DirectAdmin with the DNS area area all set, and in fact they are. The really odd thing is that domains already hosted on my server are NOT affected.

I have narrowed the issue down to being a problem with something on my server. I have an account with Enom so when a new user purchases a domain name, they really are purchasing it from Enom. It's also configured so that their name servers upon purchasing (or transferring) forward to my server of ns1.modemnet-dns.com so that their DNS can be fully controlled via DirectAdmin on my server. When any new account is setup this way, trying to ping the new domain name comes back with 'unresolved' type of errors.

But if I goto Enom manually to use their DNS hosting and them create the A/Cname/Mail records on their server, then it works fantastically. Does anyone have any idea what could be causing this?? Even logged in to SSH on my server I'm unable to ping the domain names that are new.

Help!!

Brad

 

[nobaloney]

Either the zone files aren't being setup properly on your server, or Enom is taking a while to update the main root servers with your nameservers, or you're setting up the wrong nameserver names on the new accounts, or you just haven't given the name enough time to resolve.

Jeff

 

[modem]

Well I can rule out not giving it enough time because I gave it over a week for it to resolve and that resolved just fine. When I modified one of my own domain names with a subdomain, it resolved within 12 hours.

I went through and checked the zone files and everything looked the same from the domain that wasn't working to the one that was. Also when the new domain was not working, I couldn't even logon to the server itself with SSH and ping it and get a response. One would think that that would be the first thing that would work when checking.

Brad

Either the zone files aren't being setup properly on your server, or Enom is taking a while to update the main root servers with your nameservers, or you're setting up the wrong nameserver names on the new accounts, or you just haven't given the name enough time to resolve.

Jeff

 

[nobaloney]

Hopefully you've been able to resolve the problem by now.

If not, you might want to check with the registrar.

Have you run the dig command with the +trace option?

Jeff

Jeff

 

[GXX]

Can you provide the domain(s) that are having problems? It might be easier to help that way.