On Feb 17, 8:47am, Colin Campbell wrote:
> I have exactly the same problem. For reasons other than sane ones my internal
> DNS has the following structure:
> primary for 158 in-addr.arpa domains (C and subnets of A, B nets)
> primary for 49 of the following domains
> secondary for 62 in-addr.arpa domains
> secondary for 3 domains in gov.au
> One day I hope to have many of the primaries hosted by the people who own
> In a situation like this the only solution is for me to primary and secondary
> and everyone to forward to me. None of the features of BIND (4.9.5) nor the
> patches permit anything else.
Yes. I have never quite understood why bind doesn't allow me to
define NS (and glue) entries for domains in the cache file. These
records would never timeout. Then all I need do is ensure that my
internal info is kept up-to-date, and restart the server any time there
is a change (not difficult).
----------- Gordon Lack ----------------- gml4410 @
The contents of this message *may* reflect my personal opinion. They are
*not* intended to reflect those of my employer, or anyone else.