DNS resolve order
Hello...
Network and sites:
3 sites: A, B and C.
Site A = 192.168.1.1/24 and 172.16.4.0/24
Site B= 10.0.0.0/24
Site C = 10.5.0.0/24
********************
Active Directory and DNS:
Site A has 2 DCs:
DC1 =192.168.1.1 (DNS server)
DC2 = 192.168.1.2/ 172.16.4.1 (DNS)
Site B:
RODC3 = 10.0.0.1 (DNS)
Site C:
DC4= 172.16.5.1 (DNS)
**************************
Site B can only access 192.169.1.x in site A but not 172.16.4.x.
the problem is, when a client try to resolve mydomain.com or dc2 sometime it is resolved to 172.16.4.1 which is not reachable from site B network.
AD replication works fine with out issue as Site A is the hub and replicate to other sites.
Is there a way to configure DNS to response to clients queries in site B from mycompany.com with 192.168.1.1 always not 172.16.4.1 ? in other words, I want all clients in site B to be able to communicate with DC1 or DC2 in 192.168.1.1 vlan.
DCs are mix of 2012 and 2012 R2.
Thanks!
Network and sites:
3 sites: A, B and C.
Site A = 192.168.1.1/24 and 172.16.4.0/24
Site B= 10.0.0.0/24
Site C = 10.5.0.0/24
********************
Active Directory and DNS:
Site A has 2 DCs:
DC1 =192.168.1.1 (DNS server)
DC2 = 192.168.1.2/ 172.16.4.1 (DNS)
Site B:
RODC3 = 10.0.0.1 (DNS)
Site C:
DC4= 172.16.5.1 (DNS)
**************************
Site B can only access 192.169.1.x in site A but not 172.16.4.x.
the problem is, when a client try to resolve mydomain.com or dc2 sometime it is resolved to 172.16.4.1 which is not reachable from site B network.
AD replication works fine with out issue as Site A is the hub and replicate to other sites.
Is there a way to configure DNS to response to clients queries in site B from mycompany.com with 192.168.1.1 always not 172.16.4.1 ? in other words, I want all clients in site B to be able to communicate with DC1 or DC2 in 192.168.1.1 vlan.
DCs are mix of 2012 and 2012 R2.
Thanks!
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
Thank you guys for your answers and good ideas that provided.... I totally agree that mutli-homed DC is not a good idea and needed to be changed. is there any official document explains the issues of having multi-home DC ?
my plan to get rid of the second nic in that DC, but need to convene the management.
my plan to get rid of the second nic in that DC, but need to convene the management.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks a lot!
access DNS of site B from Primery Domain and check the forwarder point to your primary domain ..
on Site B domain you should have the primary dns of the same domain and secondary point to your main site primary domain.
all the best