lame-servers: error (FORMERR) resolving [something]

[Daniele]

Thank you.

So it's not my responsibility to resolve the problem, right?

The point is that, sometimes, I can't resolve an address because of this
lame servers, and dig (for example) fails.

Is it possible?


2013/1/8 Shane Kerr <shane at isc.org>

> Daniele,
>
> On Tuesday, 2013-01-08 09:49:57 +0100,
> Daniele <d.imbrogino at gmail.com> wrote:
> > Hi all.
> >
> > Sometimes I can't resolve some addresses and, in the logs, I can find
> > the message in the title:
> >    lame-servers: error (FORMERR) resolving [something]
> > (where `something` is the address I'm trying to resolve).
> >
> > What does it means?
>
> When acting as a recursive resolver, BIND 9 follows the chain of
> delegation from the root, contacting name servers identified for each
> domain on the way.
>
> In this case, one of those name servers returned a packet that BIND 9
> did not like for some reason - a FORMat ERRor. The offending server is
> marked as "lame" since it cannot answer queries for the domain in
> question.
>
> The message should also include the IP address of the server that it is
> going to at the end of the line.
>
> > And how can I resolve this problem?
>
> In theory, you could try contacting the administrator of the server at
> that IP address, and letting her know that there is some technical
> problem so she can resolve it.
>
> In practice, this is a worthless message and you should disable it in
> named.conf:
>
>     logging {
>         category lame-servers { null; };
>     };
>
>
>
> A couple of questions to everyone on the list...
>
> 1. Should ISC change the default logging for lame servers to disabled?
>
> 2. Are there other usually worthless default log messages we should
>    disable?
>
>
> Cheers,
>
> --
> Shane
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130108/733e9481/attachment.html>