acrodriguez
asked on
DNS zones on separate subnets under same AD Domain Name.
I have two nets. 192.168.1.x and 192.168.2.x. My 192.168.1.x hosts my DC with primary DNS zone (domain.org) and AD. I have the nets connected by VPN. What zone file should I use for my 192.168.2.x net. The DC on 192.168.2.x, I installed on as a additional domain controller within the same domain.org AD Domain. It replicates fine with the DC on 192.168.1.x. What zone type should I use and what zone name can I use? I have not had time to finish my MCSE yet so I'm designing and learning as I'm going along. The DNS is my last piece of the puzzle. I have DHCP on the 192.168.2.x DC and the DNS is setup for the 192.168.2.x, then 192.168.1.x and then the DNS of the ISP's.
ASKER
Netman66. Thank you. So, make the remote site have it's own primary zone with Active Directory Integrated. Correct? I also added reverse address lookups for security. Your opinion please?
If the Main site has Zones that are AD Integrated, then you only have to install DNS on the server - you do not need to create ANY zones. Replication will create them for you. In fact, if you do create them you will cause them to be out of sync.
I suppose the Reverse Zone can be created since it differs from the main site.
I suppose the Reverse Zone can be created since it differs from the main site.
ASKER
My apologies for my ignorance here. In reading about Active Directory Integrated DNS, when using different sites with different subnets, it was best to use a DC with DNS on all subnets all under the same domain name each as a Global Catalog Server especially when using VPN's. Your saying I don't have to add a primary zone to the DNS server at the remote site because it will cause sync problems between the DNS systems. The replication will handle everything. I'm using a cost of 50 on the DEFAULTIPSITELINK because the VPN connections are T-1's.
So what about redundancy if I lose the DC at the main site? How will the remote site handle the issue if the primary zone is not present?
So what about redundancy if I lose the DC at the main site? How will the remote site handle the issue if the primary zone is not present?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Make sure the remote DC is pointing to the main site's DNS server only.
Simply install DNS on the other DC and wait.
All zones should replicate to the remote server from the parent.
Once complete, point the remote server to itself for DNS and all the clients on this subnet should point to it also.
Configure Forwarder to the ISP on both networks - do not Forward from the remote site to the parent site (there's no point since all records on both servers should be the same).