Re: Draft internic ip allocation doc
...
Well, you can delegate these as 128 individual zones. With a little bit of automation to help, it may approach practical. You can delegate a single domain name in the limiting case.
But this doesn't really save anything in terms of the amount of work that has to be done by the NICs and probably increases it, as when the ISP's clients want to be primary for their IN-ADDR.ARPA domains, the delegation records will have to be updated to list extra servers. -- Chris Chaundy (Network Manager) connect.com.au pty ltd, P.O. Box 2202, Caulfield, Victoria 3161, Australia Internet: chris@connect.com.au Phone: +61 3 9528-2239 Fax: +61 3 9528-5887
...
Well, you can delegate these as 128 individual zones. With a little bit of automation to help, it may approach practical. You can delegate a single domain name in the limiting case.
But this doesn't really save anything in terms of the amount of work that has to be done by the NICs and probably increases it, as when the ISP's clients want to be primary for their IN-ADDR.ARPA domains, the delegation records will have to be updated to list extra servers.
The NICs need not be involved; they've already delegated the larger blocks to the ISPs who can then, if they wish, delegate the smaller blocks to their clients. louie
...
Well, you can delegate these as 128 individual zones. With a little bit of automation to help, it may approach practical. You can delegate a single domain name in the limiting case.
But this doesn't really save anything in terms of the amount of work that has to be done by the NICs and probably increases it, as when the ISP's clients want to be primary for their IN-ADDR.ARPA domains, the delegation records will have to be updated to list extra servers.
Actually, it does save. The NICs (and down stream providers) get extra levels of heirarchy that get delegated. Once delegated, the load is considerably less. -- --bill
participants (3)
-
bmanning＠ISI.EDU -
chris＠connect.com.au -
Louis A. Mamakos