Solved

NSLOOKUP Default Server suddenly is .com instead of .local

Posted on 2008-10-31
6
314 Views
Last Modified: 2012-06-27
Suddenly for no known reason all my workstations are attempting to resolve thru my .COM instead of .LOCAL. In my primary location I have my DCs running mydomain.LOCAL, all my workstations in the same standard /24 subnet are all joined to mydomain.LOCAL. I have a satellite location connect by VPN where I have mostly only servers running mydomain.COM. I do have an in & out Realm transitive trust setup between the two. Nothing major has changed in the last 2 months and then today in the middle of the day my I received complaints that sites ending in mydomain.COM were not resolving from mydomain.LOCAL workstations. A closer look into the situation I see that when I do a NSLOOKPUP on any mydomain.LOCAL workstation it says:

C:\>nslookup
Default Server:  colodc01. mydomain.COM
Address:  10.0.172.10

However, to further confuse matters all of my Servers in mydomain.LOCAL say correctly:

C:\>nslookup
Default Server:  caldc01.mydomain.LOCAL
Address:  172.27.23.34

I have a temporary fix with resolving those mydomain.COM websites simply by adding those to the colodc01.mydomain.LOCAL DNS. That's fine to do, they were never needed there because nothing should route through that satellite location.

The bigger issue is what's shown in nslookup, and it looks like I may be having some A/D issues as well relating to this. Any clue to why this happened or better yet how to fix it? I check all the basic stuff, and even those most of my workstations are using DHCP, even those that are static are also having this issue. All workstations are having this issue.
0
Comment
Question by:p1techservices
  • 2
  • 2
6 Comments
 
LVL 13

Expert Comment

by:Rowley
ID: 22848316
Does the dns servers IP specified in the LOCAL clients network config match that of 10.0.172.10?
0
 

Author Comment

by:p1techservices
ID: 22850342
No, all (dot) LOCAL clients only have a DNS server of (dot) LOCAL DCs which is 172.27.23.34 & .30. As far as the. LOCAL clients are concerned they should not even know that .COM or the 10.0.172.x exist.
0
 
LVL 13

Expert Comment

by:Rowley
ID: 22850610
At a guess, sounds like you're running split-dns and it's got its knickers in a twist. Have you checked your DHCP servers scope settings? Also, are there any rogue ptr records for caldc01.mydomain.LOCAL anywhere? Has anyone added another IP or interface to a server somewhere?

You're absolutely sure that nobody has changed anything?
0
 

Author Comment

by:p1techservices
ID: 22906953
I did find the answer to this. to start with i removed the Group Policy and that did not help so i made a new policy forcing it to point everything to the right domain .local. then i got into the Active Directory and made some changes to force it to resolve suffix to .local. then i found the IP address in the reg under dns client of 10.0.172.10 which should not have been there so i fixed that. after all this gpupdate would not clear all the systems effected but this issue so i removed the systems from the domain to flush the domain policy then rejoined it to the domain so it would get the new domain policy and it works now. plus the network is in better shape now too.
0
 

Accepted Solution

by:
ee_auto earned 0 total points
ID: 24670681
Question PAQ'd, 500 points refunded, and stored in the solution database.
0

Join & Write a Comment

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…
In this article, we will see the basic design consideration while designing a Multi-tenant web application in a simple manner. Though, many frameworks are available in the market to develop a multi - tenant application, but do they provide data, cod…
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 to another domain controller. Log onto the new domain controller with a user account t…

759 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

22 Experts available now in Live!

Get 1:1 Help Now