troubleshooting Question

NSLOOKUP Resloving wrong IP for local server

Avatar of Steve Marin
Steve MarinFlag for United States of America asked on
DNSWindows Server 2008
5 Comments1 Solution3209 ViewsLast Modified:
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
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 5 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros