nslookup shows that it cannot resolve its own name

Posted on 2008-11-17
Last Modified: 2012-05-05
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.
Question by:tgrizzel
    LVL 19

    Assisted Solution

    Is there a record in the Reverse Lookup Zone in DNS...on this server?
    LVL 3

    Accepted Solution

    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).

    Author Comment

    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?
    LVL 19

    Expert Comment

    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 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.

    Author Comment

    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.  

    Author Comment

    Ill award points on this tomorrow.... Did anyone get a chance to look at the link above that points to my other issue?

    Author Closing Comment


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    One of the most often confused topics in the area DNS is the idea of GLUE records. Specifically, what they are, when they are needed, when they are provided, and how they are created. First, WHAT IS GLUE? To understand GLUE, you must first under…
    There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now