Link to home
Start Free TrialLog in
Avatar of MX370JL
MX370JL

asked on

nslookup resolves the correct IP address, but the wrong server name

I have just set up a new active directory domain.  On the domain controller I have DNS running.  From a command prompt, I type:

nslookup [my domain name]

The server name and ip address are displayed, but the server name is not correct.

I can do "ping -a [my ip address]" and the name is resolved correctly.  I'm doing all this command line stuff from the domain controller.

What did I do wrong and how do I fix it?
ASKER CERTIFIED SOLUTION
Avatar of ryansoto
ryansoto
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of MX370JL
MX370JL

ASKER

in dnsmgmt, there is nothing under Reverse Zones.  

I click on the revers zones folder and there is nothing there.
This can occur for several reasons:

1.  Several computers have registered the PTR record and haven't cleaned up
2.  The primary name of the server is different to the one you are using.  It is quite common for servers to have several DNS forward-lookup records associated with them
Avatar of MX370JL

ASKER

Uhhhh..........

I just set the DC up and its the DC I'm looking up, so it shouldn't be using any other name.  The name that nslookup displays is a server that hasn't been on my network for a couple years.

Let's say my DC's name is: PlantDC
And its IP is: 10.10.10.1
And my domain name is: Plantfloor

from the cmd window on the DC I type:
nslookup Plantfloor

it returns:
Server: BackupExecServer (an old server that hasn't been on the net in years)
IP: 10.10.10.1

I don't know how another computer especially BackupExecServer would have registered anything on this DNS server(also the DC), which I set up today.  
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You can use an IP address with lserver rather than relying on a DNS lookup.
Avatar of MX370JL

ASKER

I think I figured it out.

I created a reverse lookup zone on my new DNS and added the host I was looking for, now everything resolves fine.  Although my old DNS server was not explicitly configured in my TCP\IP config, the server must have been getting the wrong name from an old DNS server.
Glad to help.