DNS Errors 4015, 4004. Bad Reverse lookup Zone.

Dell SC1420, with SBS2003 (Standard Ed).
Single network adapter.
Internet connection via ADSL Router (Netgear DG834)

Server is PDC on small network (9 workstations).

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).

ipconfig /all
Connection specific DNS suffix: balston.local
DHCP Enabled: No
IP Address:
Subnet Mask:
Default Gateway
DNS Servers:

nslookup balston.local
Server: UnKnown
Name: balston.local

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
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?


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sam PanwarSr. Server AdministratorCommented:
I have had the exact same problem. My Dell rep recommends reinstalling the operating system, perhaps a bit extreme. We were able to delete the reverse lookup zone by changing it to a non active directory zone. However, when the server is rebooted, the zone comes back and it is active directory, and the errors come back.  Wish someone had an answer to this one because I am not looking forward to reinstalling the operating system.
I managed to fix this problem. I followed a method I found in a tech article that I don't have the link for (I am at home now!) though I will be able to give you the link on Monday.
In short, I used the old NT4-era shut-everything-down-uninstall-reinstall-restart process - in which everyone of those dashes is a full power-off reboot! If I had a rubber chicken I would wave that over the server as well, just to be sure! ;-)
What I figured was that the older network I had connected to had somehow got remembered by the system, so I first shut down the DNS processes, server and workstation, took the server physically off the network, uninstalled the MS DNS, and this next bit was the crucial bit...
Open the Server Manager, and open the Active Directory section. Under the View menu, change the view to Advanced. Many more directories show up, one of which should be MSDNS. It was under this tree that I found a reference to the old subnet that kept 'magically' reappearing. I deleted this reference (after writing down the settings, just in case I was doing Something Bad). I also did a hunt through the registry for that subnet just to be sure I had got everything.
Another reboot, and I reinstalled the DNS - and it all came back up! I barely had to do a thing, just add a reverse-lookup zone for our new subnet - and the wizard just about did that for me. The full-log nightmare was gone!
As I mentioned, I am at home, and that is my recollection of what I did. I kept a reference to the tech note I found at work; I can send that on Monday. If you are feeling brave before then, I would advise doing a full backup of everything - after all I am an Architect, not an IT professional!

Forums solution:


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
keithxpAuthor Commented:
Well our situations are even more simple, I am a Landscape Architect and not an IT professional!!

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?


keithxpAuthor Commented:
I meant our situations are even more alike....
MSSPs - Are you paying too much?

WEBINAR: Managed security service providers often deploy & manage products from a variety of solution vendors. But is this really the best approach when it comes to saving time AND money? Join us on Aug. 15th to learn how you can improve your total cost of ownership today!

keithxpAuthor Commented:
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."


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.


keithxpAuthor Commented:
Thanks - I am very familiar with that entry on eventid.net. I could almost recite it...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.