bind - forwarders

Kevin Darcy kcd at daimlerchrysler.com
Mon Feb 26 23:07:00 UTC 2001


I am not completely sure what you are asking. However, be aware that in
BIND 8.2.3, forwarders are selected based on how fast they respond to queries.
This is different from previous BIND versions, where the forwarders were tried
sequentially according to the order in which they were listed in the forwarders
{ } clause.


- Kevin

Takaaki Iwamoto wrote:

> Hello, I am TAKAAKI.
>
> bind-8.2.3 are used in solaris2.5.1 environment,
> furthermore it is the composition of DNS outside inner DNS->Gateway->.
> It has, when outside DNS falls with forwarding the name
> resolution of an external domain to outside DNS, and in the setup of inner DNS,
> it was made to forward to secondly DNS in a provider side.
>
> <Inner DNS>
> option{
>        forwarders {
>                 1.2.3.4;      // Outside DNS
>                 5.6.7.8;      // secondly in a provider side
>                 5.6.7.9;      // secondly in a provider side -2
>         };
>         forward only;
> }
>
> However, snoop | grep DNS, then the transfer are working only to secondly
> by the side of a provider in inner DNS, and most transfers to
> outside DNS were not generated. Although an order different knows
> the order of reference, it is strange that it is only secondly in provider.
> On a timeout, that is, a course, outside DNS is the nearest reason
> and it is hard to consider it. If secondly in provider side is commented out,
>  it will come to forward to outside DNS perfectly.
>
> Although it thinks that there is more environment same probably,
> what does it act as you?





More information about the bind-users mailing list