We help IT Professionals succeed at work.

Windows 2008 R2 DNS Problem

shutterhacker
shutterhacker asked
on
This is a simple one domain as forest root domain, with two DCs. Now the on both of DCs DNS the zone's SOA has "server." instead of FQDN. The zone's NS records are duplicate with both "server." and FQDN records.
Comment
Watch Question

Author

Commented:
See attached screen cap.

As a result, the exchange 2010 (on DC grouse) won't start (ADtopology service won't start). The SOA can be manually edited to FQDN and the NS records "server." can be deleted but they came back to that way right after editing/deletion.
Screenshot-2015-02-28-14.50.33.png

Author

Commented:
It appears the guy responsible for the domain did something on one of DCs treasure on 1/2/2015. Right after he restarted treasure, its DNS log's server name switched to single level (first screen). And NETLOGON service on both DCs started to log error (2nd and 3rd screens). After that, all client PCs fail to register their names in DNS. The guy kept entering static records for the PCs to keep it going.
Screenshot-2015-02-28-01.14.45.png
Screenshot-2015-02-28-01.06.06.png
Screenshot-2015-02-28-00.49.18.png

Author

Commented:
Until 2/26, the system still went on like it was. Then 2/26 5:40pm the other DC grouse was restarted.

Author

Commented:
Right after he restarted grouse, the DNS log on grouse also switched to single level name (see screen cap). Then the AD is entirely down.

I was asked to have a look at the situation. Ran dcdiag /test:dns /v returned many warnings and errors. Not sure what to do at this point.
Screenshot-2015-02-28-15.29.02.png

Author

Commented:
Any thoughts?
Top Expert 2014
Commented:
You're missing a record or two...

Name                        Type            Data            Timestamp
(same as parent folder)     Host (A)        10.0.0.12       <recent date>
(same as parent folder)     Host (A)        10.0.0.x        <recent date>                (whatever TREASURE's IP is)

Open in new window


Under the _msdcs branch in that view, what do you have?
Under the DomainDnsZones branch what do you have?
How is the DNS config of the network interfaces on your DCs? Please post an ipconfig /all of the systems.

Any hint what the guy resp. for the domain did?
Principal Support Engineer
Commented:
Do those servers have a primary DNS suffix configured? Go to System Properties, Advanced System Settings. In the Computer Name tab, click Change, then click More to see the primary DNS suffix. If it's blank, type your AD domain name in the field and click OK. A reboot will be needed for the change to take effect.
Top Expert 2014

Commented:
^^^ if they don't they're not Domain Controllers!
DrDave242Principal Support Engineer

Commented:
^^^ if they don't they're not Domain Controllers!
A DC must have a primary DNS suffix when it's initially promoted (in fact, it should acquire one during the promotion if it wasn't previously a domain member), but it's possible to remove it afterward. I've just done it via the GUI in my test environment, so it could also presumably be done via an errant (or malicious) script, regedit, or Powershell cmdlet.

My test DC from which I removed the primary DNS suffix is now showing the same symptoms as the OP's DC:

DNS event 414 on my DC

Author

Commented:
Just to close the thread - the other guy is going to take care of it. Thanks all for the response.