Reverse Lookup Config for Multiple Networks

  • Thread starter Thread starter Zach
  • Start date Start date
Z

Zach

Hello,

I have a question regarding reverse lookup zones. We have several different
VLANs on our network and we're in the process of installing Windows Server
2003. For example, we have the following:
192.100.10.x
192.100.100.x
192.100.200.x
192.200.10.x
192.200.100.x
192.200.224.x

Should we create a reverse lookup zone for each of these or, should we
create a reverse lookup zone for 192.100.x.x and 192.200.x.x? I noticed
that if I create a reverse zone for 192.100.x.x and then right click on it,
I have an option called "New Domain." This allows me to enter the next
octect such as 192.100.10.x. A folder named "10" will then appear
underneath the reverse lookup zone for 192.100.x.x. Is this the right way
to do it? Also, does anyone have a KB article that talks about this?
Thank you,

Zach
 
<my_opinion>

I would create a reverse zone for each subnet.

</my_opinion>

Zach said:
Hello,
Click to expand...
I have a question regarding reverse lookup zones. We have several different
VLANs on our network and we're in the process of installing Windows Server
2003. For example, we have the following:
192.100.10.x
192.100.100.x
192.100.200.x
192.200.10.x
192.200.100.x
192.200.224.x
Click to expand...
 
Joe's suggestion should work fine.

My comments are actually based on these IP addresses you posted. They are
actually public IP address that are registered to other corporations or
entities. For instance, 192.100.10.x range belongs to NASA and 192.100.200.x
rqange belongs to Universidad Nacional Autonoma de Mexico.

In all honesty, I would suggest to use one of the private IP ranges or you
may want to go to a website or send mail to someone with these IPs, it will
never get there, besides conflicting wtih a public IP.

These are private ranges:

192.168.0.0/16 (Can handle 65.534 IPs)
172.16.0.0/19 (can handle 8192 IPs)
10.0.0.0/8 (Can handle 16,777,216 IPs)

:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Zach said:
Hello,

I have a question regarding reverse lookup zones. We have several
different VLANs on our network and we're in the process of installing
Windows Server 2003. For example, we have the following:
192.100.10.x
192.100.100.x
192.100.200.x
192.200.10.x
192.200.100.x
192.200.224.x

Should we create a reverse lookup zone for each of these or, should we
create a reverse lookup zone for 192.100.x.x and 192.200.x.x? I
noticed that if I create a reverse zone for 192.100.x.x and then
right click on it, I have an option called "New Domain." This allows
me to enter the next octect such as 192.100.10.x. A folder named
"10" will then appear underneath the reverse lookup zone for
192.100.x.x. Is this the right way to do it? Also, does anyone have
a KB article that talks about this?
Thank you,

Zach
Click to expand...

Your method will work fine, one note, if you set the zone to allow dynamic
updates DDNS registration will complete the zone and create the PTR records
for you.
 
Back
Top