Cannot contact other DNS Server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have 9 windows 2003 domain servers in a forest and each DC has DNS. When I
try to open DNSmgmt, the DNS server opens locally. If I want to connect to
other DNS server in the domain, Cannot contact the DNS server. NSlookup works
fine. Why is it that I cannot connect to remote DNS server.
 
Hello Zareer,

There was a Vulnerability some month ago for DNS KB 935966, maybe you or
some other admin has configured the registry entry for shorttime solution,
described in this article?
http://www.kb.cert.org/vuls/id/555920

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
 
In
Zareer Bhathena said:
We have 9 windows 2003 domain servers in a forest and each DC has
DNS. When I try to open DNSmgmt, the DNS server opens locally. If I
want to connect to other DNS server in the domain, Cannot contact the
DNS server. NSlookup works fine. Why is it that I cannot connect to
remote DNS server.

Zareer,

In addition to MyWeb's question, exactly how are you trying to connect in
the console? Are you using IP address of the other DNS server, it;s FQDN or
it;s NetBIOS name?

Are the other DCs on the same subnet or are they spread across remote sites?

My initial thought is you are trying to connect via NetBIOS name and the DCs
are across remote sites and you are not using WINS. But then again, I may be
wrong. Looking forward to your response.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Try using Outlook Express or any other newsreader, configure a news
account, and point it to news.microsoft.com. Anonymous access. It's
easy and it's free:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Life isn't like a box of chocolates or a bowl of cherries or
peaches... Life is more like a jar of jalapenos. What you do today
may burn your butt tomorrow." - Garfield
 
I tried to connect other DNS server by Server name. I also tried by IP
address, and finally I tried by FQDN which is server name.domain.com
All three different ways gives the same result. cannot contact other DNS
servers. I tried to add a host entry on one dns server and I am able to see
the change on all 9 DNS servers which tells me dns is working.
 
In
Zareer Bhathena said:
I tried to connect other DNS server by Server name. I also tried by IP
address, and finally I tried by FQDN which is server name.domain.com
All three different ways gives the same result. cannot contact other
DNS servers. I tried to add a host entry on one dns server and I am
able to see the change on all 9 DNS servers which tells me dns is
working.

If you cannot connect by using the IP and FQDN resolves to an IP, then it
comes to either an authentication issue, DNS is not working on that machine,
or there are ports being blocked between locations possibly blocking RPC
(135). If that is the case, I would also assume other important ports are
being blocked and you may be having replication errors on the DCs.

Use portqry from Microsoft to determine if all ports are open between
locations.

New features and functionality in PortQry version 2.0This article discusses
the new features and functionality that are available in PortQry Command
Line Port Scanner version 2.0. PortQry version 1.22 is a ...
http://support.microsoft.com/kb/832919

Portqry Examples
http://technet2.microsoft.com/WindowsServer/en/library/4b5b7cad-cf35-48cb-af98-a733fba361ad1033.mspx

Portqry to troubleshoot Exchange: (more examples)
http://support.microsoft.com/kb/310298



Ace
 
Back
Top