The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.
You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
Main Topics
Browse All Topics





by: oBdAPosted on 2009-09-25 at 13:06:56ID: 25426776
Check if there's a pointer record for 192.168.1.13 in your reverse lookup zone for 192.168.1.0.
If so, delete it, wait until the deletion has replicated to the other DNS server, then open a command prompt on the server in question, and enter
ipconfig /registerdns