win 2003, dns exchange problems
I set up a windows 2003 domain controller, and a 2003 member server for exchange 2003. There appears to be a DNS issue. if I do a NSLOOKUP from either machine I get: DNS request timed out. timeout was 2 seconds. default server unknown, address 192.168.10.7. If I try to install exchange on the member server I get: setup encountered an error while trying to contact the windows active directory. the error was:
failed to lookup the windows site to which this computer belongs. please verify that your computer and the domain controller designated as the schema master used the same preferred DNS server. that your computer is configured with correct site information and is in a windows domain where the domain controller is reachable.
Both the servers and workstation are using the ip address of the DC running DNS for thier primary DNS server.
Error inthe dns log
Event Type: Warning
Event Source:DNS
Event Category:none
Event ID: 4521
Date:4/4/2007
Time:3:10:47 PM
User:N/A
Computer: VALS1
Description:
The DNS server encountered error 32 attempting to load zone 1.168.192.in-addr.arpa from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
failed to lookup the windows site to which this computer belongs. please verify that your computer and the domain controller designated as the schema master used the same preferred DNS server. that your computer is configured with correct site information and is in a windows domain where the domain controller is reachable.
Both the servers and workstation are using the ip address of the DC running DNS for thier primary DNS server.
Error inthe dns log
Event Type: Warning
Event Source:DNS
Event Category:none
Event ID: 4521
Date:4/4/2007
Time:3:10:47 PM
User:N/A
Computer: VALS1
Description:
The DNS server encountered error 32 attempting to load zone 1.168.192.in-addr.arpa from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
ASKER
that should cure the issue of the dns timeouts? I will try it in the morning.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm having the same problem, where I have two servers running DNS, and only one of them is having this problem, DNS is replicating between them, if i delete the zone will it effect the other DC(the one without the error)?
often you can ignore them, however i would delete your zones out of DNS, Then restart the netlogon service and run ipconfig /registerdns on your DC
Regards,
James