NSLOOKUP Default Server suddenly is .com instead of .local

Posted on 2008-10-31
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:

Default Server:  colodc01. mydomain.COM

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

Default Server:  caldc01.mydomain.LOCAL

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.
Question by:p1techservices
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
LVL 13

Expert Comment

ID: 22848316
Does the dns servers IP specified in the LOCAL clients network config match that of

Author Comment

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

Expert Comment

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?

Author Comment

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

Accepted Solution

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

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
trying to change time server to, errors 2 36
Change local account password via GPO? 34 68
Multiple Errors from DCDIAG 2 21
SSL-VPN 1 45
This article runs through the process of deploying a single EXE application selectively to a group of user.
Last week, our Skyport webinar on “How to secure your Active Directory” ( provided 218 attendees with a step-by-step guide for…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

740 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