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

Windows 2000 DNS Reverse lookup with subnetted network

I have tricky problem that I am sure someone else must have came across. I have created a new child domain in AD for my company; I have an up most domain called company.com then a lower domain called ext.company.com. In the ext.company.com I have created 2 domain controllers and assigned the relevant FSMO roles and GC etc etc but I am having a problem with reverse lookup with regards to the DNS Setup.

I have setup reverse lookup before and it’s pretty simple BUT I have a subnetted IP address for both DNS servers i.e.

DNSDC1
10.5.212.22
255.255.240.0

DNSDC2
10.5.216.22
255.255.240.0

I am stuck because in a normal classful IP network the network ID for the in-addr.apra is simple to work for instance my test system has the ip

192.168.100.10
255.255.255.0

So the reverse lookup name would be 100.168.192.in-addr.apra as the network part of the IP address is 192.168.100 but with my production system my network ID is 10.5.208 due to the subnet mask. Obviously if I put this in then I will never be able to do a reverse lookup on 10.5.212.22. I have done some research and found RFC2317 but I am finding it heavy going and as I don't want to delegate this DNS domain I am not sure it’s the right document to solve this problem.

My only other thought is to create a separate in-addr.arpa for each classful subnet but I am not sure if there is a better way to do this or if that will even work.

Anyone else hit this wall with regards to reverse lookup and solved it?

Your help would be appreciated…

Thanks again

Gareth



Windows 2000 SP4 all hotfixes installed...

0
pubeheed
Asked:
pubeheed
1 Solution
 
svenkarlsenCommented:
Have you actually tried adding 10.5.208.0 to the DNS reverse lookup and found that it didn't work ?

Anyhow, as I see it, the DNS does not relate to subnets as we configure them ;-)

Depending on how many boxes on my LAN, I would either make 1 reverse lookup zone (10.5.x.x, - don't enter any trailing zeroes when you create it) or 1 zone for each of your 16 subnets from 10.5.208 - 10.5.223.

As you will see by testing and using the "Update PTR...." in properties of e.g. any A-record, both solutions works fine.
0
 
pubeheedAuthor Commented:
Hello,

Thanks for help with this one I ended up adding a 5.10.in-addr.apra reverse lookup zone. When new hosts are added it automatically created sub folders of 212 and 216. This enables the reverse lookup to work, without too much config.

Thanks again

Gareth
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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