Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

too many timeouts - disabling EDNS

182 views

Skip to first unread message

Binmakhashen, Latif

unread,

Aug 15, 2008, 3:55:38 PM8/15/08

After upgrading to bind-9.5.0-P2, I get many of the following message in
the log. Is this something I need to worry about or can I just suppress
it?

I don't' get a response from the command line for the domains associated
with the error and I don't seem get anything about most of them from
using dnsstuff.com free tools either?
So I'm just curious what are those domains? Is it safe to suppress the
EDNS messages. I didn't see that before the upgrade, I was running
bind-9.3.2.

Aug 15 15:45:23 named[10612]: too many timeouts resolving
'ns1.e-fastcash.com/AAAA' (in 'e-fastcash.com'?): disabling EDNS
Aug 15 15:45:27 named[10612]: too many timeouts resolving
'ns.e-fastcash.com/AAAA' (in 'e-fastcash.com'?): disabling EDNS
Aug 15 15:45:27 named[10612]: too many timeouts resolving
'ns1.e-fastcash.com/AAAA' (in 'e-fastcash.com'?): disabling EDNS
Aug 15 15:45:43 named[10612]: too many timeouts resolving
'_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.DAL.ORG/SRV'
(in 'dal.org'?): disabling EDNS
Aug 15 15:45:43 named[10612]: too many timeouts resolving
'_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.DAL.ORG/SRV'
(in 'dal.org'?): disabling EDNS
Aug 15 15:45:44 named[10612]: too many timeouts resolving
'_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.DAL.ORG/SRV'
(in 'dal.org'?): disabling EDNS
Aug 15 15:45:53 named[10612]: too many timeouts resolving
'pharma011.dal.org/A' (in 'dal.org'?): disabling EDNS
Aug 15 15:45:55 named[10612]: too many timeouts resolving
'pharma011.dal.org/A' (in 'dal.org'?): disabling EDNS

Thanks

-- NOTICE --
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material, the disclosure of which is governed by
applicable law. Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon, this information
by persons or entities other than the intended recipient is
prohibited. If you received this in error please contact the sender
and destroy the materials contained in this message.

Andrey G. Sergeev (AKA Andris)

unread,

Aug 15, 2008, 4:11:49 PM8/15/08

Hello Latif,

Fri, 15 Aug 2008 15:55:38 -0400 Binmakhashen, Latif wrote:

> After upgrading to bind-9.5.0-P2, I get many of the following message
> in the log. Is this something I need to worry about or can I just
> suppress it?

Are there any SOHO routers between the box on which BIND is running and
your ISP?

Same results here:

[andris@maroon ~]$ dig e-fastcash.com. ns

; <<>> DiG 9.5.0-P2 <<>> e-fastcash.com. ns
;; global options: printcmd
;; connection timed out; no servers could be reached

> Aug 15 15:45:43 named[10612]: too many timeouts resolving
> '_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.DAL.ORG/SRV'
> (in 'dal.org'?): disabling EDNS
> Aug 15 15:45:43 named[10612]: too many timeouts resolving
> '_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.DAL.ORG/SRV'
> (in 'dal.org'?): disabling EDNS

As for these messages - try to check with your AD administrator.

> Aug 15 15:45:53 named[10612]: too many timeouts resolving
> 'pharma011.dal.org/A' (in 'dal.org'?): disabling EDNS
> Aug 15 15:45:55 named[10612]: too many timeouts resolving
> 'pharma011.dal.org/A' (in 'dal.org'?): disabling EDNS

Got SERVFAIL result from the 218.232.110.133 and 222.122.218.55.

Yours sincerely,

Andrey G. Sergeev (AKA Andris) http://www.andris.name/

Mark Andrews

unread,

Aug 15, 2008, 11:34:47 PM8/15/08

The log should get less noisy in the next release.

2409. [bug] Only log that we disabled EDNS processing if we were
subsequently successful. [RT #18029]

Currently the log indicated when we have disabled EDNS processing
due to timeouts. Mis-handling of EDNS queries or the responses are
not the only cause of timeouts.

Note just about all versions of named disable EDNS processing on
timeout. This however impacts on DNSSEC processing as DNSSEC
requires EDNS.

The log message is there to highlight potential problems.

Mark

> After upgrading to bind-9.5.0-P2, I get many of the following message in
> the log. Is this something I need to worry about or can I just suppress
> it?
>

> I don't' get a response from the command line for the domains associated
> with the error and I don't seem get anything about most of them from
> using dnsstuff.com free tools either?
> So I'm just curious what are those domains? Is it safe to suppress the
> EDNS messages. I didn't see that before the upgrade, I was running
> bind-9.3.2.
>

> Aug 15 15:45:23 named[10612]: too many timeouts resolving
> 'ns1.e-fastcash.com/AAAA' (in 'e-fastcash.com'?): disabling EDNS
> Aug 15 15:45:27 named[10612]: too many timeouts resolving
> 'ns.e-fastcash.com/AAAA' (in 'e-fastcash.com'?): disabling EDNS
> Aug 15 15:45:27 named[10612]: too many timeouts resolving
> 'ns1.e-fastcash.com/AAAA' (in 'e-fastcash.com'?): disabling EDNS

> Aug 15 15:45:44 named[10612]: too many timeouts resolving

> '_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.DAL.ORG/SRV'
> (in 'dal.org'?): disabling EDNS

> Thanks
>
> -- NOTICE --
> The information transmitted is intended only for the person or
> entity to which it is addressed and may contain confidential and/or
> privileged material, the disclosure of which is governed by
> applicable law. Any review, retransmission, dissemination or other
> use of, or taking of any action in reliance upon, this information
> by persons or entities other than the intended recipient is
> prohibited. If you received this in error please contact the sender
> and destroy the materials contained in this message.
>
>

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_A...@isc.org

0 new messages