Problems after 8.3.3 upgrade
Nick Hengeveld
nickh at yaga.com
Tue Jul 16 23:47:28 UTC 2002
On Tue, Jul 16, 2002 at 04:38:12PM -0700, Doug Barton wrote:
> akamai name servers have problems with EDNS requests. By default, bind
> 8.3.3 sends EDNS probes to name servers when starting a lookup sequence.
> However, in my experience BIND 8.3.3 generally falls back to non-EDNS
> queries and then everything is happy.
It looks like one can disable EDNS on a per-server basis; would it make
sense to do this for all Akamai servers and hope they don't change often,
or can/should it be done globally?
Also, would that explain why the problem goes away when I force a cname
lookup?
> The behavior you describe below is quite odd.... are you 100% sure that
> you're running 8.3.3 on your resolvers? I ask because:
>
> ; <<>> DiG 9.2.0
>
> If you are using 9.2.0 by chance, you should definitely upgrade to 9.2.1.
My workstation is running 9.2.0 from the Mandrake RPMs. The servers are
all running 8.3.3:
[nickh at ops named]$ /usr/sbin/named -v
named 8.3.3-REL Fri Jun 28 22:36:09 PDT 2002
nickh at v1.dev.yaga.com:/home/nickh/rpm/BUILD/bind-8.3.3/src/bin/named
[nickh at backup nickh]$ /usr/sbin/named -v
named 8.3.3-REL Fri Jun 28 22:36:09 PDT 2002
nickh at v1.dev.yaga.com:/home/nickh/rpm/BUILD/bind-8.3.3/src/bin/named
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
More information about the bind-users
mailing list