General discussion

Locked

MS DNS, some domains do not resolve

By Curacao_Dejavu ·
I am having trouble understanding some of the explications while generating a report on wirelesscuracao.com.
I am receiving some errors, as can be seen below.
The setup is as follows on netsol:
magnum.wirelesscuracao.com: 63.245.44.2
magnum.pancarib.com: 63.245.44.2
ubique.wirelesscuracao.com: 63.245.45.2
ubique.pancarib.com: 63.245.45.2

In addition to this on the nt 4 based dns server I am receiving the following error message in eventviewer.
eventid 7062: Dns server encountered a packet addressed to itself.

in addition (2), if I do a nslookup with my server's ip , it wont lookup the domain.
but if I do root, and than the domain it will resolve it.


Can you help me correct these problems ?

The error message at dns report is:
FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly.
ubique.wirelesscuracao.com.
magnum.wirelesscuracao.com.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example). FAIL Missing nameservers 2

ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
magnum.pancarib.com.
ubique.pancarib.com.

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to MS DNS, some domains do n ...

yeah I've seen this. What happened here was our DC running AD DHCP DNS RRAS on one box took a dump, we had another DC running on the net but it wasn't running DHCP RRAS and the lot. when the main DC came back up, we started to get these errors. We also started getting DNS and connector errors from Exchange Server. When we demoted the DC without DHCP RRAS so on and so forth to a member server the problems seemed to go away even the errors out of Exchange disappeared. Seemed pretty quirky to us. This was BEFORE the JPEG & GUI hoxfixes if you were wondering.

Collapse -

by CG IT In reply to

What we eventually concluded was that because we didn't duplicate the entire services strucure that the server with DHCP,RRAS etc etc had with the 2nd DC when that server went down, the 2nd DC was trying to pick up the slack but we goofed. DHCP went down and well so clients looking for services couldn't reach a DNS server even though we had on on the net. DHCP provided clients with DNS info and since it was off line, well ooops. We goofed is the bottom line.

Collapse -

by Curacao_Dejavu In reply to

This is a stand alone NT box, which only function is DNS services

Collapse -

by Curacao_Dejavu In reply to MS DNS, some domains do n ...

This question was closed by the author

Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums