Bind 9.1.0 cache problem?

Owen McShane omcshane at vianetworks.co.uk
Mon Feb 5 15:52:43 UTC 2001


I don't actually see the connection here.

On further investigation into my original mail, it seems that fasthosts are 
not running Bind, and that the Bind 9.1.0 is refusing to talk to them, but is 
returning the following:

Feb 05 14:01:19.661 info: client 127.0.0.1#2063: query: fasthosts.co.uk IN SOA
Feb 05 14:01:19.661 debug 3: client 127.0.0.1#2063: query approved
Feb 05 14:01:19.662 debug 3: client 127.0.0.1#2063: replace
Feb 05 14:01:19.662 debug 3: clientmgr @0x4017ffc8: createclients
Feb 05 14:01:19.662 debug 3: clientmgr @0x4017ffc8: recycle
Feb 05 14:01:19.662 debug 1: createfetch: fasthosts.co.uk. SOA
Feb 05 14:01:19.662 debug 3: fctx 0x4019d3f8: create
Feb 05 14:01:19.662 debug 3: fctx 0x4019d3f8: join
Feb 05 14:01:19.662 debug 3: fetch 0x4017b018 (fctx 0x4019d3f8): created
Feb 05 14:01:19.662 debug 3: fctx 0x4019d3f8: start
Feb 05 14:01:19.662 debug 3: fctx 0x4019d3f8: try
Feb 05 14:01:19.662 debug 3: fctx 0x4019d3f8: cancelqueries
Feb 05 14:01:19.662 debug 3: fctx 0x4019d3f8: getaddresses
Feb 05 14:01:19.663 debug 3: fctx 0x4019d3f8: query
Feb 05 14:01:19.663 debug 3: resquery 0x401a24e8 (fctx 0x4019d3f8): send
Feb 05 14:01:19.689 debug 3: resquery 0x401a24e8 (fctx 0x4019d3f8): sent
Feb 05 14:01:19.689 debug 3: resquery 0x401a24e8 (fctx 0x4019d3f8): senddone
Feb 05 14:01:19.707 debug 3: resquery 0x401a24e8 (fctx 0x4019d3f8): response
Feb 05 14:01:19.708 debug 1: message has 55 byte(s) of trailing garbage

Owen

> 
> 
> I'm also seeing a low-probability problem with domains that look ok.
> This problem persisted for 12 hrs and then went away after a reboot.
> 
> The problem was observed with the newest named (bind 9.1.0) and the
> newest sendmail (8.11.2).
> 
>         Feb 4 14:03:00 capsicum sendmail[640]: f14M30t00640:
>         ruleset=check_rcpt, arg1=<XXX at wsrcc.com>,
>         relay=[171.64.71.20], reject=451 4.1.8
>         <XXX at wsrcc.com>... Domain of sender address
>         YYY at Steam.Stanford.EDU does not resolve
> 
>         Feb 4 14:18:57 capsicum sendmail[2173]: f14MIu802173:
>         ruleset=check_rcpt, arg1=<XXX at wsrcc.com>,
>         relay=[209.69.43.194], reject=451 4.1.8
>         <XXX at wsrcc.com>... Domain of sender address YYY at pixi.com does
>         not resolve
> 
> The first domainname "Steam.Stanford.EDU" doesn't have an MX, but does
> have an A-record for address 171.64.71.20 .  That address does have a
> ptr for "steam.Stanford.EDU".  The capitalization is different, but
> that shouldn't make a difference.
> 
> I was working under the assumption that this was a DNS transport/cache
> problem where 9.1.0 just had a harder time getting a valid reply back.
> 
> -wolfgang
> -- 
>        Wolfgang Rupprecht <wolfgang+gnus at dailyplanet.wsrcc.com>
> 		    http://www.wsrcc.com/wolfgang/
> Coming soon: GPS mapping tools for Open Systems. http://www.gnomad-mapping.com/
> 
> 


--
 U-NET Ltd, a Via Net.Works Company 
 Local Touch Global Reach 
 Owen McShane		Systems Administrator
 http://www.u-net.net	Tel +44 (0)1925 484444




More information about the bind-users mailing list