Determining Which Authoritative Sever to Use (Bob McDonald)

Bob McDonald bmcdonaldjr at gmail.com
Sun May 8 16:46:42 UTC 2022


Thanks for the answers. A couple more questions and then I'll stand down.

First, it's Ben Croswell. Just pointing that out.

Second, my reading of the definition of a static-stub zone in the Bvarm
indicates that its use is to allow a local copy of the NS list which may
differ from the primary zone. I'm not sure that's what I'm looking for. I
think I'm ok with the NS list from the primary zone. Lei me take another
swing and try to be a bit more pedantic to see if that helps.

I wish to define a global internal DNS environment.

At the level closest to the client would be a global network of recursive
DNS servers which would handle all internal and external DNS requests. The
internal DNS zones would be housed on a global network of authoritative
only DNS servers. The NS list for the internal DNS zones on these
authoritative only servers would be known to the recursive servers via stub
zones. My question is, if a client in Mumbai submits a DNS request to his
local recursive server for an internal authoritative only zone defined by a
stub zone statement, which authoritative only server does the recursive
server pick from the NS list and will that eventually be the "closest"
server. I'm assuming a global distribution of the authoritative servers.
E.g. Hong Kong, London, US East, US West, South Amer, etc. The use of the
stub zones in this case is to eliminate the need for an internal root. I
want to avoid lookups for example from clients in Asia being sent to
authoritative only servers in South Amer.

Bob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20220508/96dd0183/attachment.htm>


More information about the bind-users mailing list