[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1169
  • Last Modified:

nslookup returns Server UnKnown for my primary DC

-=SETUP=-
2 Windows 2003 based Domain Controllers

-=ISSUE=-
I had to relocate my primary DC FSMO/GC from one location physically to another and change it's IP. I went through the entire DNS MMC and couldn't find any of the old IP records anywhere...

Yet since the move, everytime I run an nslookup, I now get:

>nslookup google.com
Server:  UnKnown
Address:  198.82.152.160

Non-authoritative answer:
Name:    google.com
Addresses:  2001:4860:800f::93
          72.14.204.99
          72.14.204.103
          72.14.204.104
          72.14.204.147

I realize DNS is working as expected, but this "UnKnown" business irks me. I found this thread and verified that the PTR, A and NS records are all up-to-date ( http://www.experts-exchange.com/Networking/Misc/Q_20487925.html )

Can anyone else point me in the right direction or show me what I might be missing?

Thanks,
0
ovprit
Asked:
ovprit
2 Solutions
 
IanThCommented:
0
 
KCTSCommented:
The 'unknown' message is because you don't have a reverse lookup zone set up in DNS. In the vast majority of cases you don't actually need a reverse lookup zone. Its not a problem and can be ignored. If you reaaly want to create a reverse lookup zone then see http://support.microsoft.com/kb/323445
0
 
QlemoDeveloperCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now