reverse lookup zone

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hello,
what are the benefits (if any) of using a reverse lookup zone per subnet on
a subnetted network? would it be better to use one reverse lookup zone for
the whole network (i.e 168.192.in-addr.arpa instead of
2.168.192.in-addr.arpa, 3.168.192.in-addr.arpa, etc)?

thanks
 
MAX said:
hello,
what are the benefits (if any) of using a reverse lookup zone per subnet on
a subnetted network? would it be better to use one reverse lookup zone for
the whole network (i.e 168.192.in-addr.arpa instead of
2.168.192.in-addr.arpa, 3.168.192.in-addr.arpa, etc)?

thanks
Click to expand...

There are a few benefits if the IP range is public, such as for a reverse
entry for an MX record. Internally, with Windows 2003, you may get 11006
SPEGNO (I can't rememver the exact Event ID) errors with DCs that usually
occur based on a missing reverse zone. As for clients, not really needed.
It's more of a best practice to have a reverse zone. As for as what subnet,
I like to do it individually, for two reasons, organizing them by subnet,
and also so I can look in that specific subnet if I want to check out just
one of my locations, otherwise they are all in one zone, it may look
cluttered.

Hope that helps


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
In
MAX said:
Thanks Ace, I thought the same thing, I just wanted to make sure,
it's easier to look'em up this way.
Click to expand...

My pleasure Max. If you have any more questions, please do feel free to post
back.

:-)

Ace
 
Back
Top