Carlos E. R. wrote:
>
> The Wednesday 2007-04-25 at 21:27 +0100, G.T.Smith wrote:
>
>
[Stuff deleted]
> > I do not see the above after making the host
> > query (though the dns logs do not seem to have been updated for quite
> > some time and I have not made any changes the configuration in this
> > respect for one hell of a long time, so this something I need to check).
>
> Because I have this entry in /etc/named.conf:
>
> logging {
> channel lame_errors {
> file "/var/lib/named/log/named-lame-servers" versions 2 size 200k;
> severity debug 3;
> print-severity yes;
> print-time yes;
> };
> category lame-servers { lame_errors; };
> };
>
There is something a little odd going with logging to the
/usr/lib/named/log directory on my server, also I have not set up a
specific log for this type of error (but there again I have not stopped
such reports from being logged) and I have never seen a lame server
flagged (see below).
[Stuff deleted]
> > reports...
>
> Mine asks first my ISP DNS servers, then the root servers. Ie, I have
> "forward first".
>
Forward first is the default ....
What I suspect is that BT accept recursive requests on their DNS and
any DNS requests are resolved by the BT DNS server pool and the results
are returned as authoritative. In your case (and the original case) the
ISP DNS server does not accept recursive requests and supplies a
referral if it does not have the address in cache, or returns a
non-authoritative response that sets off a trawl of the root servers ....
The former does make sense as for BT, the latter well ... it is an
operational decision...
[Stuff deleted]
>
> It maybe coincidental and not intentional, but who knows.
>
This is a bit problematic... a lame server is a server that BIND detects
as responding in a broken manner, now this could be stiil be referring
on to the refusing servers which may be refusing because they are being
hit by an awful lot of traffic. A coincidence unlikely, an accident
plausibly.. deliberate hmm....
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
