• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 830
  • Last Modified:

windows 2008 r2 reverse dns multiple subnets

dear gurus, good day to you all

i do have a query for knowlede base to follow the gurus way

- we have below sites
HO 10.0.1.0/24
DR SITE 10.0.6.0/24
BRANCH A 10.0.2./24
BRANCH B 10.0.9./24
BRANCH C 10.0.3./24
BRANCH D 10.0.10./24

- i have placed master AD/DNS server HO site, where 1 member dns/ad kept in dr site, beside each site has their own DNS/AD(additional or member domain controller)

- the issue is with reverse dns, how to do step by step any tips and guideline for such cases,
- do u have to do reverse dns of all above subnet at master server? and dr server?
- i want to place each site, in client machine ips master dns ip, dr dns ip, and that site or branch local dns ip, 3 dns to keep running
- in any case if 1st dns fail go to 2nd, if 2nd fail go to 3rd etc.
- to reduce the traffic network congestion i prefer each users/clients must report to local dns of that site only then try something else (like HO or DR site) or vice verse

ideally what work around on HO, DR and Sites/branches

all sites are interlinked by vpn

kind regards
salim
0
tmsa12
Asked:
tmsa12
1 Solution
 
SandeshdubeySenior Server EngineerCommented:
Reverse lookup zone is not created automatically you need to create the same.Reverse lookup zones and PTR resource records are not necessary for Active Directory to work, but you need them if you want clients to be able to resolve FQDNs from IP addresses. Also, PTR resource records are commonly used by some applications to verify the identities of clients.See below link how to add reverse lookup zone.
 
Adding a Reverse Lookup Zone
http://technet.microsoft.com/en-us/library/cc961414.aspx

Note as the zone will be AD integrated the same will be replicated to other Dcs in the network.

Regarding the dns setting on client and DC see this:
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/

You also need to ensure that AD sites and service is configured correctly.Map the subnet to correct AD site so that client can authenticate to local DC.http://technet.microsoft.com/en-us/library/cc736820(WS.10).aspx

See this DC locator process for more info:http://blogs.technet.com/b/arnaud_jumelet/archive/2010/07/05/domain-controller-locator-an-overview.aspx http://technet.microsoft.com/en-us/library/cc978011.aspx
0
 
tmsa12Author Commented:
thank you can you close the case plz
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now