Solved

server DNS issues

Posted on 2014-02-05
7
341 Views
Last Modified: 2014-02-15
I have five DC's, one at each site. For some reason, on my main DC, the DNS entry for one of the other servers is missing. I am unable to ping that server via hostname. I can reach it by IP and everything else seems to be fine. When I look at WINS, the entry is there. When I look at DNS, the entry is missing. I try to manually add it and I get the following error.

"Warning: The associated Pointer (PTR) record cannot be created, probably because the references reverse lookup zone cannot be found."

When I right click on the forward lookup zone and go to the name servers tab, the server I am unable to ping does not show the IP address, it says unknown. I tried to correct this yesterday but this morning it was back to unknown again.

How do I correct this DNS entry?

Thanks,

Justin
0
Comment
Question by:JustinGSEIWI
  • 4
  • 2
7 Comments
 
LVL 53

Expert Comment

by:Will Szymkowski
ID: 39836002
The error maessage is pretty self explanitory, Do you have your reverse lookup zone setup properly for the subnet at the remote site?

Have you checked the DNS logs on the server to see if there have been some recent activity that might have casued this IP to be removed from DNS?

If you login to your domain controller that is no longer listed and run the following command does it update DNS accordinlgy?

- start>run>cmd
- ipconfig /registerdns

See if that works for your DC.

Also check the KB regarding this issue.
DNS Server Reverse Zone Lookup Error

Will.
0
 
LVL 79

Expert Comment

by:David Johnson, CD, MVP
ID: 39836254
Why are you using WINS? NT clients?
0
 

Author Comment

by:JustinGSEIWI
ID: 39836380
I believe the reverse lookup zone is setup properly. It was working fine for the longest time and then I Just noticed it is having issues.

I did a nslookup and this happened.

C:\Users\administrator>nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  ::1

I also did ipconfig /registerdns but that doesn't look like it did anything. I manually corrected the DNS entry and it is working now but I did that yesterday and it was not working again this morning. When I look at the DNS entry in the forward lookup zone, the timestamp is blank instead of saying static like the other servers do.

I found the following in the event log two weeks ago. No other events have been logged since this log.

Log Name:      DNS Server
Source:        Microsoft-Windows-DNS-Server-Service
Date:          1/24/2014 4:49:02 PM
Event ID:      4015
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

I have windows setup because a consultant told me it is just good to have setup. I am guessing for old XP machines? There is no harm in having it setup so I just left it.

Justin
0
Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 

Author Comment

by:JustinGSEIWI
ID: 39836829
I corrected the DNS for the host earlier today when I made my last host. As of now, the DC cannot ping the other DC again.
0
 
LVL 53

Expert Comment

by:Will Szymkowski
ID: 39837705
What are you DNS settings set to? Do you have DNS logging enabled? If you have logging enabled it will be able to tell you why your DC is getting removed from DNS.

Enable DNS Logging

Will.
0
 

Accepted Solution

by:
JustinGSEIWI earned 0 total points
ID: 39848665
I enabled scavenging and then restarted DNS and the issue appears to be resolved now. Not sure if scavenging fixed it or why it would of fixed it?

Justin
0
 

Author Closing Comment

by:JustinGSEIWI
ID: 39861166
scavenging appeared to of fixed the issue
0

Featured Post

Does Powershell have you tied up in knots?

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

Question has a verified solution.

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

One of the most often confused topics in the area DNS is the idea of GLUE records. Specifically, what they are, when they are needed, when they are provided, and how they are created. First, WHAT IS GLUE? To understand GLUE, you must first under…
There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

867 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now