A lot of DNS Errors "DNS Operation Refused" & DNS RR set that ought to

[ftoddt]

I inherited this and can only assume that it was configured badly. I am extremely weak in DNS and am considering uninstalling it and starting over. Here are my errors: What if I just deleted those records. These errors come from a backup domain controller. The primary has the same errors. We are Windows 2000 with a few xp clients that this is wreaking havoc with. Thanks for looking.

Registration of the DNS record 'dd9a3da6-5cac-4b2e-865f-fa3709ce159e._msdcs.internal.waterville.wednet.edu. 600 IN CNAME wsd-bc.internal.waterville.wednet.edu.' failed with the following error:
DNS RR set that ought to exist, does not exist.

Registration of the DNS record '_kerberos._tcp.Default-First-Site-Name._sites.internal.waterville.wednet.edu. 600 IN SRV 0 100 88 wsd-bc.internal.waterville.wednet.edu.' failed with the following error:
DNS operation refused.

Registration of the DNS record '_kerberos._tcp.internal.waterville.wednet.edu. 600 IN SRV 0 100 88 wsd-bc.internal.waterville.wednet.edu.' failed with the following error:
DNS operation refused.

Registration of the DNS record '_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.internal.waterville.wednet.edu. 600 IN SRV 0 100 88 wsd-bc.internal.waterville.wednet.edu.' failed with the following error:
DNS operation refused.

Registration of the DNS record '_kerberos._tcp.dc._msdcs.internal.waterville.wednet.edu. 600 IN SRV 0 100 88 wsd-bc.internal.waterville.wednet.edu.' failed with the following error:
DNS operation refused.

I had configured a cache only DNS server on my Isa but took it off later. These errors are frequent and are prevent some virtual telnet sessions on XP.
Any and all help is appreciated.
Todd

 

[ChicagoTechNet]

quoted from

http://www.chicagotech.net/

How to clear bad information in Active Directory-integrated DNS

You may need to clear bad information in Active Directory-integrated if DNS is damaged or if the DNS contains incorrect registration information. To do that, 1) Change the DNS settings to Standard Primary Zone.
2) Delete the DNS zones.
3) Use ipconfig /flushdns command.
4) Recreate the DNS zones.
5) Restart Net Logon service
6)Use ipconfig /registerdns


Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[ftoddt]

Thank You very very much.
This is great information. It is Active Directory Intergrated. You have given very clear directions but being new to this, I am not real sure I understand it all. I am not sure about this:
1) Change the DNS settings to Standard Primary Zone.
I am not sure what this means. I only see the server name under the DNS with the Forward Lookup Zone and the We have a single doamin of about 200 computers at a small school. All computers are on the same domain as well as the servers. The servers are all Win2k and consist of a primary domain controller (which has one DNS) a backup domain controller(which has a secondary DNS which may not be configured as secondary but rather Active Directory Intergrated like the primary), an ISA server, a file/print server, exchange server and a website server. Most client computers are W2k but some are XP Pro which I have had nothing but DNS problems with since they arrived 6 months ago(20 min logins).
Also would I need to do the flushdns command on all the computers within the LAN.
I was also wondering if instead of deleteing the DNS Zones, could I just uninstall and reinstall DNS on that Domain Controller. You also mentioned that if DNS is Active Directory Intergrated that their may be some bad information in the Active Directory itself. Is there any common problems that I should look for.
I thank you so much for your time. Since I had two machines with DNS, I had planned on disconnecting the secondary from the LAN and uninstalling the DNS and reinstalling the DNS on the Primary that would still be connected to active directory. Then I could copy all the MX, A, SOA etc records from the unplugged secondary that I know for sure that I need, do the dns flush and dns register and see how it works from there. If it fails, I can use the backup. Will I have to wait for the new DNS to take affect like you do when those records are put out on the web.
Thanks again for your help and all advice is greatly appreciated.
Todd