JustinGSEIWI
asked on
server DNS issues
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
"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
Why are you using WINS? NT clients?
ASKER
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>nsl
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-Serv
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
I did a nslookup and this happened.
C:\Users\administrator>nsl
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-Serv
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
ASKER
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.
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.
Enable DNS Logging
Will.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
scavenging appeared to of fixed the issue
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.