Corrupt Reverse DNS

Hi All,

I have a client that has a Windows SBS 2003, it is a single domain controller, single DNS Server.

The reverse DNS has become corrupted and wont load any more. The DNS is AD integrated, not file based.
I need to know how to remove the corruption from AD, I have taken a snapshot of the server so I am safe in that regards.

Does anyone have a walkthrough about removing the corrupt records. I have been reading through this website and was going to complete the tasks, but I have also read on different EE forum entries that it doesnt work.

http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/44342/clear-DNS-information

Any DNS masters input would be great as I am still limited on my understanding of DNS and AD.

Cheers
LVL 1
H0ff3RAsked:
Who is Participating?
 
DraxonicCommented:
My suggestion would be to change the DNS Service to a standard DNS service instead of an Active Directory DNS service.

You can then take the text file and edit it with any text editor (I would probably import it into Excel for easier data manipulation and editing).

You can then stop the DNS service, replace the text file with your edited copy, start the DNS service again. You can then change it back to an AD integrated DNS zone if you wish.

0
 
H0ff3RAuthor Commented:
Hi Draxonic,

Thanks for the quick reply.

Forgive my ignorance about DNS though, Can you do this on the fly or is this better suited to afterhours?
I understand that changing the file etc would be relatively quick and restarting the service would not impact the users to a great deal, but the initial change to file based and the change back to ad integrated, would that take a long time and will it impact then?

Cheers
0
 
DraxonicCommented:
Just to clarify the above, by "standard DNS service" I'm  referring to what Microsoft call a "Standard Primary".

The files will be stored in the %SystemRoot%\System32\Dns folder as .dns type files.

You can also use the command:
dnscmd /ZoneExport FQDN_of_zonename Zone_export_file
...to export the AD Integrated DNS data to a text file.
0
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
DraxonicCommented:
No worries H0ff3R.

I would expect this to take only seconds on a small service like this that is a single server business.

Having said that, I tend to err on the side of caution, so I would probably do this after hours anyway, just in case something went wrong unexpectedly and I needed time to fix it.
0
 
DraxonicCommented:
Thanks for your confidence H0ff3R, but I would generally advise that you should implement a suggested solution before marking it as correct/accepted. You may find that the suggested solution doesn't work or requires refinement.

Cheers,
Drax
0
 
H0ff3RAuthor Commented:
Draxonic,

Just a quick follow up - I ran your suggestion of dnscmd /ZoneExport FQDN_of_zonename Zone_export_file and looked at the file. It doesnt have any reference about the reverse dns information. Would this be in refernce to the corruption?

Cheers
0
 
DraxonicCommented:
The FQDN of the reverse DNS zone for a subnet of 192.168.1.0 will be in the format:

1.168.192.in-addr.arpa

Note that the digits are in reverse and exclude the host part of the address and it uses the in-addr.arpa suffix.



0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.