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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
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.
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.
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
Cheers,
Drax
ASKER
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
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
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.
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.
ASKER
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