ChocolateRain
asked on
Stub Zone Problems 2008 R2 DNS Servers (windows 2008 r2 dns stub zone validation error: Please try again later))
I'm trying to setup a Trust between domains but before I can do that I need to setup a Stub Zone on both DC/DNS servers on both domains.
I can setup a Stub Zone on the new DNS/DC to our old DNS/DC server but I can't setup a Stub Zone on our old network to point to the new network. Everytime I try to setup a Stub Zone it gives me the windows 2008 r2 dns stub zone validation error: Please try again later).
I don't know what could be causing this to work on one server and not another. Already checked the obvious firewall issue and basic TCP/IP connectivity between servers.
I can setup a Stub Zone on the new DNS/DC to our old DNS/DC server but I can't setup a Stub Zone on our old network to point to the new network. Everytime I try to setup a Stub Zone it gives me the windows 2008 r2 dns stub zone validation error: Please try again later).
I don't know what could be causing this to work on one server and not another. Already checked the obvious firewall issue and basic TCP/IP connectivity between servers.
ASKER
I didn't setup IPSec or DNSSec on the new domain controller.
On the old DC I have a Warning Event when i run the DNS BPA tool but i don't have any warnings or errors in the event log for the old DC/DNS server.
The warning on this old server is: Title:
DNS: Valid network interfaces should precede invalid interfaces in the binding order
Severity:
Warning
Date:
9/8/2010 2:23:40 PM
Category:
Configuration
Issue:
A disabled or invalid adapter precedes a valid adapter in the network interface binding order list.
Impact:
The binding order determines when network interfaces will be used to make network connections by the computer. A disabled adapter high in the binding order can degrade performance.
Resolution:
Click Start, click Network, click Network and Sharing Center, and then click Manage Network Connections to move all disabled and invalid interfaces to the bottom of the binding order list.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=121966
This is a funny error message to receive since there are no other adapters in this machine (it is a virtual machine btw).
On the old DC I have a Warning Event when i run the DNS BPA tool but i don't have any warnings or errors in the event log for the old DC/DNS server.
The warning on this old server is: Title:
DNS: Valid network interfaces should precede invalid interfaces in the binding order
Severity:
Warning
Date:
9/8/2010 2:23:40 PM
Category:
Configuration
Issue:
A disabled or invalid adapter precedes a valid adapter in the network interface binding order list.
Impact:
The binding order determines when network interfaces will be used to make network connections by the computer. A disabled adapter high in the binding order can degrade performance.
Resolution:
Click Start, click Network, click Network and Sharing Center, and then click Manage Network Connections to move all disabled and invalid interfaces to the bottom of the binding order list.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=121966
This is a funny error message to receive since there are no other adapters in this machine (it is a virtual machine btw).
Have you went here to check the binding order?
Click Start, click Network, click Network and Sharing Center, and then click Manage Network Connections to move all disabled and invalid interfaces to the bottom of the binding order list.
Make sure that your primary NIC is listed first.
Click Start, click Network, click Network and Sharing Center, and then click Manage Network Connections to move all disabled and invalid interfaces to the bottom of the binding order list.
Make sure that your primary NIC is listed first.
ASKER
There is only 1 network connection under the standard options as well as the Binding options.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have 3 old DCs that all do this when trying to connect to the new DC.
Everything is virtualized using VMware.
I got it working by checking the allow Zone Transfers box and had to select the "Allow Zone Transfers" and select the option box "To Any Server". If I tried to isolate this by Hostname, FQDN or IP address it errored out.
Can you see why I'm getting rid of the old domain?
=]
Everything is virtualized using VMware.
I got it working by checking the allow Zone Transfers box and had to select the "Allow Zone Transfers" and select the option box "To Any Server". If I tried to isolate this by Hostname, FQDN or IP address it errored out.
Can you see why I'm getting rid of the old domain?
=]
Any 'interesting' errors in the DNS Log on either DCs?