custom nameserver and dns issues

browncow

Verified User
Joined
May 15, 2006
Messages
12
I added a new domain name via DA named Right2know.org.

When I do nslookups and trace routes, the IP appears to resolve correctly.
However, when I go to dnsreport.com and check the domain, I get errors:

I registered ns1.browncownetworks.com as 67.53.106.5 at my registrar.
I registered ns2.browncownetworks.com as 67.53.106.6 at my registrar.

I created NS records under admin section for browncownetworks.com
I also created A records for ns1 and ns2 under the browncownetworks.com domain.

http://dnsreport.com/tools/dnsreport.ch?domain=right2know.org

ERROR. One or more of your DNS servers are missing A records (per NS records that may be cached). As a result, they cannot be used. The problem hostnames are:

ns2.browncownetworks.com. has no A record.
ns1.browncownetworks.com. has no A record.

NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled.

I think I am close to begin migrating my websites over to my new DA server once I get these custom DNS issues resolved.
Also, is there no IMAP server installed part of DA?

Thanks for the help.
Can't believe how fast DA is over Plesk 7.5, which I am trying to migrate from.
 
I woke up this morning and tried dnsreport.com again for my right2know.org domain and now everything is working correctly.

I already manually stopped and started named via DA when I was suspecting perhaps it wasn't picking up my changes.

Can anybody clue me in why problems would just go away without me actually doing anything?

Its been 2 days and I'm already so much happier with DA than Plesk 7.5....woohoo!

Thanks.
Hao.
 
Because DNS takes time (up to two days or so) to propagate.

You can check to see if your server accepted the change from the command line:
Code:
dig @localhost example.com
or from your windows desk/lap/top (making substitutions as necessary):
Code:
> nslookup
> server ns1.example.com
> domain.example.com
Jeff
 
Back
Top