Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently working on a network with multiple subnets. So far I have implemented one reverse DNS entry that is a monolithic 10.* record covering everything. Is there any benefit or performance boost for creating a granular structure allowing look-ups to occur quicker? Or is this more work than I need to perform?

share|improve this question
up vote 1 down vote accepted

Generally speaking this is more work than you need to perform -- Most DNS servers can handle a /8 dumped in one file without batting an eyelash in terms of performance.

Having said that, traditionally reverse zones (for IPv4) are broken out as Class C (/24) netblocks -- C.B.A.IN-ADDR.ARPA (because dots are the hierarchy delimiter in DNS names, and there used to be a similar hierarchy in Class A/B/C IP addresses).
That also has the benefit of keeping the zone file "small" (250ish entries), which can be easier for admins (and some badly written DNS management user interfaces) to read & manage.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.