Bind 812 vs 822 and forwarders

[Kevin Darcy]

Well, there may very well be a bug here, but since you have changed 2 things at
once, if there is a bug it would be hard to tell whether it's something to do
fundamentally with the forwarder logic or just a configuration-file parsing
bug.

Does forwarding work with BIND 8.2.2-p5 with *exactly* the same config file you
were using with BIND 8.1.2? That would help narrow down the problem.

By the way, BIND 8.2.3 is now officially released. Maybe this is a bug that's
already been fixed.


- Kevin

Diego Balgera wrote:

> Hi,
> I'm having a problem in implementing the forwarders feature in a bind
> 8.2.2P5 installation.
> What I did in the previous Bind 8.1.2 host was (I'm reporting here the whole
> "options" section):
>
> options {
>         directory "/etc/named.data";    // running directory for named
>         // query-source address * port 53;
>         forwarders { 10.20.10.12; };
>         forward only;
> };
>
> With Bind 8.2.2P5 I used the same, only adding a few sortlist:
>
> options {
>         directory "/etc/named.data";    // running directory for named
>         // query-source address * port 53;
>         forward only;
>         forwarders { 10.20.10.12; };
>         rrset-order { class IN type A name "mnc010.mcc222.gprs" order
> random; };
>         sortlist {
>                 { 10.20.10.0/24;
>                         { 10.20.10.20;   10.20.10.30; };
>                 };
>         };
> };
>
> The forwarding feature in Bind 8.2.2 doesn't work, and the host could not
> reach the target dns.
> I couldn't find any difference in the syntax between Bind 812 and 822, do
> you know if I'm wrong in something or there is a bug somewhere?
>
> Thank you in advance.
> Diego.