Sporadic DNS problems after DA reinstall

modem

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

I've had noticeable DNS problems that appear sporadically ever since I had to reinstall DirectAdmin back in December. One of these problems is getting emails from a certain website. When their emails were being delayed by upto 12 hours, I contacted their system admin, who checked their logs and said that their email servers couldn't look up my email domain/website (modemnet.net). They copied me a piece of the logs that showed that only after trying for 8-12 hours could their email servers recognize/resolve modemnet.net.

This lead me to inspect the issue more closely, and I noticed issues with DirectAdmin and my DNS. For example, prior to re-installing DA, I would goto Admin/"Your User" -> "Domain Administration" -> "Add Another Domain" and then create a domain like 'beta.modemnet.net'. (modemnet.net is a name I own and it's already managed under Domain Administration). The new beta.modemnet.net name would almost instantly work and show up via any web-browser.

Now after reinstalling DA, when I follow this same procedure to create beta1.modemnet.net, beta2.modemnet.net, etc they are never recognized by any browser. In fact, they are not even pingable. This is even after several days giving the DNS servers time to propipgate the information through the internet.

Does anyone have any idea what might be causing this?
 
Hey,

Being the DNS servers for modemnet.net are ns1.modemnet-dns.com and ns2.modemnet-dns.com and they are both the same address which is the same address as modemnet.net.... whew...

My first guess would be you're not telling your DNS servers about the beta1.modemnet.net when you add it...

When you create the (sub)domain beta1.modennet.net (whose parent is modemnet.net) you have to tell your DNS servers ns1/ns2.modemnet-dns.com where to find beta1 or else no one will be able to find it.

Of course, I could just be confused.

David
 
Also make sure the new zone exists and that your DNS server is restarting after you careate the new zone, so it gets loaded.

Both beta1.modemnet.net and beta2.modemnet.net are resolvable here.

Jeff
 
Back
Top