segunda-feira, 30 de abril de 2012 00:30
I'm working through the IPAM lab and encountering errors in the DNS zone monitoring section. My environment is a WS2012 Hyper-V host / DC, with an IPAM server and a DHCP server, all on an internal network. The domain name is sandbox.test. In the DNS Zone Monitoring section, both the sandbox.text and _msdcs.sandbox.test forward zones are showing errors.
Basic connectivity between the servers is working just fine. I've run DCDIAG /TEST:DNS /V and it comes up clean, no DNS errors. The DNS server (the host) is showing green in the Server Inventory section. I haven't found anything in the "Understanding and Troubleshooting IPAM" document that describes how to fix this situation, and I'm giving an IPAM demo in a couple of days at a conference so it'd be nice to get it working :).
- Tipo Alterado Tiger LiModerator sexta-feira, 4 de maio de 2012 08:51
Todas as Respostas
terça-feira, 1 de maio de 2012 08:09Moderador
Thanks for posting here.
Have we set the firewall exception on both DNS and IPAM server in order to allow RPC/WMI/WS-Management traffics to pass through on both servers . Maybe we can just temporarily disable Windows built-in firewall and retry during the testing:
IP Address Management (IPAM) overview
TechNet Community Support
quinta-feira, 10 de maio de 2012 22:29
I have added a zone with the same name to my IPAM server but it doesn't show errors.
Please try resetting the zone status and then click Tasks and retrieve server data. Let me know if this helps.
sexta-feira, 11 de maio de 2012 06:10
It looks like the Beta release did not have the ability to reset status, but this is coming.
You might have run into a bug in Beta where the zone is not correctly reset back to OK status after an error is detected. You can check the DNS event log to verify this, but it sounds like this might be what has happened since DCDIAG results are fine.
From the Understand and Troubleshoot Guide:
- IPAM displays a list of all forward lookup zones that are hosted by managed DNS servers with their overall status based on status from all the servers hosting that zone, as well as duration that the zone has been in that state. The zone status for all servers is shown as OK if the zone is being serviced by each of the Authoritative servers. The zone status for all servers is shown as Warning, if one or more authoritative servers is not servicing the zone. The zone status for all servers of the zone is shown as Error if none of the authoritative servers are servicing the zone. An authoritative server is considered to be servicing the zone if the zone status of the zone on that server and the server availability state of the server are not in red state.
I hope this helps,
sexta-feira, 11 de maio de 2012 16:18
I've been in communication with the product team and there are some known problems with DNS error events causing red status in IPAM and then not being cleared later. This should be fixed in RC, and as I mentioned you can also reset the zone status. In Beta, it is necessary to delete the error events (1004, 1201, 6527 & 503) from the DNS event log, then remove and re-discover the DNS server.
quinta-feira, 11 de outubro de 2012 17:08
We have RTM now, but it looks like the issue is still here... My DNS log is clean for the last year - and I have red status for the zone in IPAM anyway.
So I "Reset zone status", cleaned DNS Events (all of them) in DNS mmc and Retrieved Information from the DNS in IPAM console. After that zones come green.
Greg, what do you mean "delete the error events ... from the DNS event log"? Can we delete events from Event Viewer selectively?
Alex Ignatenko | MCSE/Private Cloud |MCITP:Lync 2010, Messaging, Server 2008 | MCTS:UC Voice, Virtualisation, SCCM
quinta-feira, 11 de outubro de 2012 19:15
AFAIK you cannot delete only certain events from the event log. You must clear the log, which it looks like you did and this worked. It shouldn't be required to clear the log however for status to change from red to green (in the RTM version of IPAM) when a DNS problem is fixed. I'll run some tests myself and see if I can reproduce this.