NSLOOKUP Default Server suddenly is .com instead of .local
Posted on 2008-10-31
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.