Strange DNS behaviour with Domain Controllers

Hi there,

I have a really strange behaviour with DNS when asking for the name of a Domain Controller.
A while ago whenever i used the IP address to ask for the hostname of a DC, i just got the hostname back.

I don't what changed but now i get all kind of other answer including the "real" hostname sometimes.
I feels like good old round robin behaviour.
--------------------------
forestdnszones.domain.local
domaindnszones.domain.local
gc._msdcs.domain.local
domain.local
--------------------------

This is not much of an issue at the moment. But when i open DHCP console and try to connect to the one of the DC it tries to do that with one theses names and that failes. So i have to login to that second DC an open the console there.
Long story short, most remote task are not possible anymore, cause the connection is done with the wrong hostname.

Has anyone heard of this or has an idea how i can analyse this issue?

Best regards,
Simon
LVL 1
PsymoniousAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
Did not understand exact question
Are you sating that you are unable to find domain controllers?

Check your NS records, Host(A) records and PTR records for all domain controllers for stale records
Also check (Same as Parent folder) Host records in DNS, they might be pointing to stale servers
Also check Domain Controller CNAME Records under _msdcs.domain.com and see if they are resolving and able to ping  correct domain controllers, if they do fail, you will get difficulties
You can delete stale CNAME records and recreate correct one
The correct GUID to create CNAME for particular DC can be found under AD sites and services\sitename\servers\servername\ntds settings properties \ general tab
0
Miguel Angel Perez MuñozCommented:
Set scavenge stale records on all DNS servers: http://technet.microsoft.com/en-us/library/cc753217.aspx
Ensure your DHCP are registering computers on DNS if they not register automatically: http://technet.microsoft.com/en-us/library/cc771732.aspx
Last one, DNS faulty (or have any kind of problem) consider remove DNS function and reinstall. I think you have your DNS infrastructure redundant, you can get your zones from the other DNS server.
0
PsymoniousAuthor Commented:
Both DCs are up and running and do not have an other issues.
I just get the wrong names back when resolving name to the IP address.

If i do a query with the IP to get a name, the Reverse Lookup Zone is used right?
When i look at the records for the DCs in the Reverse Lookup Zone i can see all the names that i listed above.

As i don't have an other setup to compare it with the production, i do not know how it should look in general.
Do you have the possibilities to check which records (for the DCs) are normally added to the Reverse Lookup Zones in a standard setup?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Miguel Angel Perez MuñozCommented:
By default, no reverse zones added (as least until 2008), when you do a direct query (name ask for IP) no reverse zones are involved, only to reverse query is used.
0
PsymoniousAuthor Commented:
I think i found the root of the issue.
Somewhen in the past i decided to do a regular export of the dns zones, so i can now compare how it looked at the beginning of april.

And when you look at these two samples, it makes totally sense that i get round-robin answers when asking for the name of a DC using the IP address.

[now]
---------------------------------------------------------------
5.1.168                  PTR      hostname.domain.local.
                        600      PTR      gc._msdcs.domain.local.
                        600      PTR      domaindnszones.domain.local.
                        600      PTR      domain.local.
                        600      PTR      forestdnszones.domain.local.
---------------------------------------------------------------

[april]
---------------------------------------------------------------
5.1.168                  PTR      hostname.domain.local.
---------------------------------------------------------------

So it seems that someone or somewhat enabled the "Update associated pointer (PTR) record" option on these records.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.