nslookup shows that it cannot resolve its own name

recently moved a DC in a seperate site from one subnet to another.  This is 1 of 3 DC's, where the other 2 are located in a diff location, diff site.  All 3 are GC's and all run DNS which replicates through AD.  Each of these servers are listed to have themselves as the only DNS server within their NIC properties.  

After moving the 1 DC to the new subnet, I began getting the following result when running nslookup for any IP/DNS name:

nslookup XXXXXX

*** Can't find server name for address XXXXXXXXXX: Non-existent domain
Server: Unknown
Address:  XXXXXXXXX  (same as above IP, as this is the DC that I am running this on)

Name: XXXXXXXX (this is the correct FQDN)
Address:  XXXXXX (this is the correct IP)

The "Unknown" is the issue, as it should be able to recognize its own name.... If i do a "hostname" in the command it shows up correct, and if I do an nslookup on any other DC or computer that is pointed to one of the other DNS servers it works just fine.  

If I change this DC to look at one of the other DC's it will then show the correct Server rather than Unknown when running a DNS lookup.

I have a feeling that this is causing me issues on my Exchange server, which uses this server (the one that cant do an nslookup on its self) for DNS queries.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Is there a record in the Reverse Lookup Zone in DNS...on this server?
You should create a reverse lookup zone based on the IP address. For ex. if your server has address, a reverse lookup zone 10.16.172-in.addr should be created (follow the wizard) and the PTR record of your servers IP address should be registered (if not add the PTR manually).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tgrizzelAuthor Commented:
OK, this is deff the issue.  I have no working knowledge of reverse DNS settings or really any DNS settings in the first place....

I now have 4 zones listed under the reverse lookup zone, the new one which covers the subnet at our new site where this DC and our Exchange server live, as well as 3 other zones which are 3 subnets which are all at our other site.  My question now would be, what needs to be listed as what in each of these zones?  When I created the new zone it created an SOA and a NS for itself in this zone, however do I need to add the other 2 DC/DNS servers into this zone? -I ask because this server that was originally having this issue, as well as the other 2 DC's/DNS servers are listed in the other zones.  

I did create a PTR in this new zone for this DC and it did take care of the nslookup showing Unknown, however I now am worried that these other zones may have incorrect info..... For instance, my mail server is technically in the same subnet/site as the DC that was having issues here.... Should I be creating an MX record in this zone for the email server?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

You don't need an MX record for your Exchange Server. Each of the Reverse Lookup Zones contains only the PTR records for the addresses in that particular subnet. Your Name Servers are also listed in there as well. So no...you don't have to have a PTR record for each of your DC's in everyone of those zones...just the DC's that belong to the zone.

Are you having any other problems with this new Domain Controller? You may not be as bad-off as you might think.
tgrizzelAuthor Commented:
check out my post here:


so no PTR for any other DC's, as no others are physically in this subnet/site, however they should be added as Name servers correct and visa versa? - I did this manually as they did not add in on there own (maybe didnt give enough time to replicate?)

BTW, this is not a new DC, but it has been freshly added to this new subnet with only a few days to test before moving the mail server from our office to the data center.  
tgrizzelAuthor Commented:
Ill award points on this tomorrow.... Did anyone get a chance to look at the link above that points to my other issue?
tgrizzelAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.