IP pool setup in DNS for ISP

I'm working on updating our DNS records so that the IP addresses in our
dial-up IP pools will resolve correctly when forward and reverse DNS
information is compared. I created sub-domains to help keep everything
organized under our domain in the forward lookup zone. After adding all of
the entries to the zone file, which isn't in production yet, the file grew
from about 15k to 850k with the addition of the roughly 26,000 addresses. My
question is will the size of this file create any performance problems once
put in production? I figured I would put these IP pools under their own
domain seperate from entries for mail, web and so on under our primary
domain. Under the domain I have a sub-domain and under that I have about 100
other sub-domains each with 254 entries for the /24. Looking for either some
reassurance that I'm doing this correctly or for a better solution just in
case my current configuration would be inviting disaster.
.

Relevant Pages

  • Re: IP pool setup in DNS for ISP
    ... > I'm working on updating our DNS records so that the IP addresses in our ... > dial-up IP pools will resolve correctly when forward and reverse DNS ... > the entries to the zone file, which isn't in production yet, the file grew ...
    (microsoft.public.windows.server.dns)
  • NSLOOKUP
    ... It's built-in to the OS and will allow you to query for ... specific DNS records. ... > by host name, by folder, or by IP addres or a portion thereof. ... > entries. ...
    (microsoft.public.windows.server.dns)