Avatar of Steve Marin
Steve Marin
Flag for United States of America asked on

NSLOOKUP Resloving wrong IP for local server

Experts,

I have two 2008 server, one is SBS and the other is standard. The SBS is the main PDC and the Standard is a secondary server. I have a issue where my users are periodically getting disconnected from MAS 200. I went to a workstation and ran nslookup and when I enter in my main pdc, which is ywmpdc01 I get this:

C:\Users\cservice>nslookup
Default Server:  ywmpdc01.yardneywm.local
Address:  192.168.1.10

> ywmpdc01
Server:  ywmpdc01.yardneywm.local
Address:  192.168.1.10

Name:    ywmpdc01.yardneywm.local
Address:  192.168.1.10

Which is correct. Now when I do the same for my MAS server which also is a secondary DNS / AD server I get this:


C:\Users\cservice>nslookup
Default Server:  ywmpdc01.yardneywm.local
Address:  192.168.1.10

> ywmmas01
Server:  ywmpdc01.yardneywm.local
Address:  192.168.1.10

Name:    ywmmas01.yardneywm.local
Address:  192.168.1.15

Which as you can see the first response resolves to the pdc. I believe this is what is causing my MAS users to get disconnected since it may be looking at the pdc IP instead of the MAS server IP. I've gone through DNS on both servers and do not see anything out of order. Here is what a workstation looks like for IP and DNS:


Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : yardneywm.local
   Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
   Physical Address. . . . . . . . . : BC-30-5B-BF-71-7C
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::eca2:c8af:1286:305c%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.160(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, August 09, 2011 12:50:29 PM
   Lease Expires . . . . . . . . . . : Tuesday, August 09, 2011 2:20:30 PM
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 247214171
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-64-FC-64-BC-30-5B-BF-71-7C

   DNS Servers . . . . . . . . . . . : 192.168.1.10
                                       192.168.1.15
                                       192.168.1.254
   Primary WINS Server . . . . . . . : 192.168.1.10
   NetBIOS over Tcpip. . . . . . . . : Enabled


I woudl greatly appreciate some further insight as to what I could do to make sure that the nslookup resolves correctly on the ywmmas01 server.

--Steve
DNSWindows Server 2008

Avatar of undefined
Last Comment
Steve Marin

8/22/2022 - Mon
abhijitwaikar

I beleive the the SBS server is also a DNS server and posted NSLOOKUP output is perfect. there is nothing to worry about.

Only make sure that both DC should point itself as preferred DNS server and each other as a alternet DNS server.

You might need to check any other things like AV, NIC card driver/firmware, physical connectivity which causes the user disconnection. Is this a issue with every user?

Also I noticed that you added gateway address is added as extra DNS IP in DHCP server for clients which is not required, I recommend you remove that IP.

Still if you think its a DNS issue then run dcdiag /test:dns on both server and check output.

Regards,
Steve Marin

ASKER
Yes the SBS is DNS and the Standard is secondary DNS. So you are saying that this is perfect output?C:\Users\cservice>nslookup
Default Server:  ywmpdc01.yardneywm.local
Address:  192.168.1.10

> ywmmas01
Server:  ywmpdc01.yardneywm.local
Address:  192.168.1.10

Name:    ywmmas01.yardneywm.local
Address:  192.168.1.15

I don't see that, unless I just don't understand. The first response is from server: ywmpdc01.yardneywm.local and gives the incorrect IP for ywmmas01, the ywmmas01 has an IP of 192.168.1.15, just as the second response says. And when I do the nslookup on ywmpdc01 both responses show IP 192.168.1.10 which is correct and is how I believe the ywmmas01 should be, meaning both responses should match.

ASKER CERTIFIED SOLUTION
abhijitwaikar

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Chris Dent

Abhijitw is absolutely right. This:

Server:  ywmpdc01.yardneywm.local
Address:  192.168.1.10

Is NsLookup doing a self-test. It's nothing to do with the name you asked for and will not be used by clients.

If you want to confirm a system is getting the right IP, run:

ipconfig /flushdns
ping ywmmas01.yardneywm.local

Everything you've posted suggests everything in DNS is absolutely fine. If you're having trouble with the system you need to look elsewhere.

Chris
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Steve Marin

ASKER
This helped thanks