Weird DNS issue

Hi Guys,

I have a simple network with 3 DC's and 2 DNS servers.

One of the DC's is my new 2012 R2 server with DNS.
The other  two DC's are 2003 - one with DNS.

The 2012 server has assumed all the FISMO roles.   The server that used to contain these roles also had DNS.   After transferring the roles to the 2012 server it has been demoted to a member server and had DNS removed.

One thing I noticed that on the older DNS server there is only one entry under the DNS in the tree and it happens to be the name of the server.

The 2012 server has TWO entries under DNS:  one is the name of the 2012 server (like on the 2003 DNS server) but it also had an entry called:    server.domain.local

It it normal to have two entries on a 2012 DNS server?

dcdiag /test:dns returns no errors on either server.

I still think something is wrong, however, as I have a 2008 R2 server that is setup as a Remote Desktop server.   It was working fine but now I cannot ping it.   Remote desktop also fails.   The server itself can surf the net and ping other servers.   However, I cannot ping it from my desktop or the above servers.   It's very weird and I suspect something in DNS.

Any ideas where to look?   I've run /flushdns on all machines I'm testing with....and everything got rebooted yesterday due to an untimely tree falling on an electrical line.

Thanks!

Ed
iteched1Asked:
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.

iteched1Author Commented:
Ok just figured out the dual dns entry issue - it's normal so I'm OK there.

The other issue persists....
0
matrix8086Commented:
You cannot ping as name, probably. Can you ping it by IP address? If the answer is no, the problem is at connectivity level, not DNS
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
iteched1Author Commented:
Well - I seem to have fixed the problem.

During the power outage I'm almost certain a particular switch stayed up the entire time.    I power cycled both (even thought the server had been previously) and now it is working.

So yup - likely a connectivity problem generated by the switch staying on while everything else was off.   I'll keep my eye on it for a bit but hopefully all is well now.

Thanks!  Ed
0
matrix8086Commented:
You're welcome! :)
Best regards!
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 2012

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.