On 4/19/06, Al Mulnick <[EMAIL PROTECTED]> wrote: > Because this is AD-Integrated, I would more likely suspect that there's a > problem with one of the records or a configuration issue vs. wholesale > corruption. The recommendation to remove the entire zone would flush that > problem out but as you mentioned it would likely throw the baby out with the > bathwater. Since elephants are best eaten in small pieces, it would be best > to isolate and troubleshoot. For example, on the domain controller, can you > use nslookup to find the domain controller itself? What about SRV records? > Is that the same with all domain controlled versions or just this one? What > other events are logged at startup? When you open the DNS MMC, do you see > anything odd? > > Removing the zone is not absolutely a bad idea if the zone is unusable > anyway. The servers would re-register themselves in about the next 12-24 > hours anyway (usually much much much quicker but you hate to give that kind > of advice willy-nilly.) > > I'm out of cliches for now, but let me know what you get with those > questions. It might also be a good idea to start considering calling > Microsoft if you need faster resolution.
Can anyone please confirm whether or not it is safe to simply delete the main forward AD DNS zone? What are the steps to recreate Thanks, ...D List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
