|I just took a new job as the sole windows admin for web hosting company, but there is a problem..... The Windows infrastructure has had no proper support/maintenance for over a year and there is a lot of damaged systems (I am the only windows systems engineer in the entire company so I have no supporting team to fallback on to ask questions if i get stuck....so I am really hoping someone online knows the answer to this query.) |
The Windows server 2003 DNS serves as our primary DNS (the zones this server is being used to hold DNS records for over 2000 of our customers public websites, it is not a member of our internal NT Domain nor does it have AD DS running on the machine). In the past when new zones were created on the win server 2003 machine we would add the FQDN of both Win 2003 DNS (primary) and the Linux DNS into the NS record.....and both would Validate OK. This validation process no longer works when we add new zones to the server it fails when trying to validate against our Linux secondary DNS, it returns the infamous error message "“The server with this IP address is not authoritative for the required zone”"
Zones that were created before this issue started are not affected, I can even remove the linux DNS from the NS records and when re-entering the FQDM for the Linux DNS it validates the IP with out any problems (I assume this is because the zone already exists on the linux DNS).