keithxp
asked on
DNS Errors 4015, 4004. Bad Reverse lookup Zone.
Hardware:
Dell SC1420, with SBS2003 (Standard Ed).
Single network adapter.
Internet connection via ADSL Router (Netgear DG834)
Server is PDC on small network (9 workstations).
IP: 192.168.0.1/255.255.255.0
Issue:
Currently, DNS is logging error Event ID 4015 and 9999 at 63minute intervals.
Historically, it as also logged error 4004.
In the DNS Snap-In, two reverse lookup zones are present.
192.168.x.x - no errors
192.168.0.x - shown with red X and message that the zone could not be loaded and to check AD is functioning (it is).
Diagnostics:
ipconfig /all
Connection specific DNS suffix: balston.local
..
DHCP Enabled: No
IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0
Default Gateway 192.168.0.2
DNS Servers: 192.168.0.1
nslookup balston.local
Server: UnKnown
Address: 192.168.0.1
Name: balston.local
Address: 192.168.0.1
Troubleshooting already tried:
1. Delete bad Reverse lookup Zone.
Not possible as it claims AD service is not available.
2. Uninstall DNS - reboot - Reinstall DNS
Previous configuration reappears including bad zone.
3. Use Change IP address Wizard to change server ip to 10.0.0.1/255.255.255.0.
Bad reverse lookup zone persists.
4. Reconfigure DNS to have Forward Lookup zones only.
Bad reverse lookup zone persists.
5. Change DNS to non-AD integrated.
Cannot change bad zone to non-AD integ. because AD service not available.
Really don't know what to do now. On MS Technet an advisor suggested reformatting and reinstalling the entire server, which seems a bit extreme.
Surely the data for DNS Reverse Lookup Zone is stored somewhere (?registry) and can be deleted?
Thanks
Dell SC1420, with SBS2003 (Standard Ed).
Single network adapter.
Internet connection via ADSL Router (Netgear DG834)
Server is PDC on small network (9 workstations).
IP: 192.168.0.1/255.255.255.0
Issue:
Currently, DNS is logging error Event ID 4015 and 9999 at 63minute intervals.
Historically, it as also logged error 4004.
In the DNS Snap-In, two reverse lookup zones are present.
192.168.x.x - no errors
192.168.0.x - shown with red X and message that the zone could not be loaded and to check AD is functioning (it is).
Diagnostics:
ipconfig /all
Connection specific DNS suffix: balston.local
..
DHCP Enabled: No
IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0
Default Gateway 192.168.0.2
DNS Servers: 192.168.0.1
nslookup balston.local
Server: UnKnown
Address: 192.168.0.1
Name: balston.local
Address: 192.168.0.1
Troubleshooting already tried:
1. Delete bad Reverse lookup Zone.
Not possible as it claims AD service is not available.
2. Uninstall DNS - reboot - Reinstall DNS
Previous configuration reappears including bad zone.
3. Use Change IP address Wizard to change server ip to 10.0.0.1/255.255.255.0.
Bad reverse lookup zone persists.
4. Reconfigure DNS to have Forward Lookup zones only.
Bad reverse lookup zone persists.
5. Change DNS to non-AD integrated.
Cannot change bad zone to non-AD integ. because AD service not available.
Really don't know what to do now. On MS Technet an advisor suggested reformatting and reinstalling the entire server, which seems a bit extreme.
Surely the data for DNS Reverse Lookup Zone is stored somewhere (?registry) and can be deleted?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I meant our situations are even more alike....
ASKER
Decided to take the plunge, backed up all the exchange mailboxes and attempted to delete the entry.
Unfortunately, I was not permitted to delete it because:
"The directory service encountered an unknown error."
<SCREAM>
I was allowed to rename it, however, to "X". I was also allowed to move it to the System folder under AD. When I reinstalled DNS, the culprit zone did not appear.
The DNS event log is error free... A bit of a cludge, but everything is working. I'll have to live with that dodgy entry in AD lurking.
thanks,
Keith
Unfortunately, I was not permitted to delete it because:
"The directory service encountered an unknown error."
<SCREAM>
I was allowed to rename it, however, to "X". I was also allowed to move it to the System folder under AD. When I reinstalled DNS, the culprit zone did not appear.
The DNS event log is error free... A bit of a cludge, but everything is working. I'll have to live with that dodgy entry in AD lurking.
thanks,
Keith
ASKER
Thanks - I am very familiar with that entry on eventid.net. I could almost recite it...
ASKER
Found the entry (0.168.192.in-addr.arpa) in MicrosoftDNS using the Advanced View as you suggest.
Rather alarmingly, when I go to delete this I get a message:
Are you sure you want to delete this object?
The selected object has other associated objects. Select those associated objects that you also want to delete.
In the window I have
Mark each selected Exchange mailbox for deletion.
This is greyed out and ticked - I cannot untick it.
Am I going to delete all my mailboxes?
Cheers.
Keith