jackiemeck
asked on
Primary DNS suddenly stopped transferring to Secondary server.
I need assistance debugging why I can no longer set up Secondary Domains against my inhouse Windows 2003 Primary DNS Server.
My inhouse Windows 2003 DNS Server is Primary. I'm using an outside service for Secondary. It is unix based...probably Tiny DNS.
I've set up over a hundred domains over the past years, without any problems. Suddenly, the Secondary service says it cannot transfer. Exact message: "zone transfer failed: master nameserver does not give 64.158.219.3 permission for AXFR". I've duplicated this behavior with a separate third party Secondary service.
Another odd behavior (this started earlier this year) is when I set up new name servers. When I click the "Resolve" button, it cannot find the IP address for two of the three, but I can ping each hostname from a command prompt.
All Primary Domains are set to "Allow Any Server". I tried specifying the above IP address as an allowed Server, but it does not work.
I confirmed with the datacenter that the firewall is not blocking DNS traffic.
I have used NSLOOKUP on Windows XP Pro with the following commands:
> nslookup
> server primarydnsserver.domain.co
> ls -d mydomain.com
...and I get a listing...no problems.
Assistance is appreciated!
My inhouse Windows 2003 DNS Server is Primary. I'm using an outside service for Secondary. It is unix based...probably Tiny DNS.
I've set up over a hundred domains over the past years, without any problems. Suddenly, the Secondary service says it cannot transfer. Exact message: "zone transfer failed: master nameserver does not give 64.158.219.3 permission for AXFR". I've duplicated this behavior with a separate third party Secondary service.
Another odd behavior (this started earlier this year) is when I set up new name servers. When I click the "Resolve" button, it cannot find the IP address for two of the three, but I can ping each hostname from a command prompt.
All Primary Domains are set to "Allow Any Server". I tried specifying the above IP address as an allowed Server, but it does not work.
I confirmed with the datacenter that the firewall is not blocking DNS traffic.
I have used NSLOOKUP on Windows XP Pro with the following commands:
> nslookup
> server primarydnsserver.domain.co
> ls -d mydomain.com
...and I get a listing...no problems.
Assistance is appreciated!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER