Bind sometimes SERVFAIL

Kevin Darcy kcd at chrysler.com
Wed Nov 18 21:09:55 UTC 2009


Luis Daniel Lucio Quiroz wrote:
> Le mercredi 11 novembre 2009 09:15:12, Matus UHLAR - fantomas a écrit :
>   
>> On 11.11.09 16:05, Pawel Rutkowski wrote:
>>     
>>> Please look below, it's normal ? Sometime servfail, sometimes nxdomain.
>>>
>>> [root at linux ~]# host 209.85.255.187 ns1.isp
>>> Using domain server:
>>> Name: ns1.isp
>>> Address: ns1.isp#53
>>> Aliases:
>>>
>>> Host 187.255.85.209.in-addr.arpa not found: 2(SERVFAIL)
>>> [root at linux ~]# host 209.85.255.187 ns1.isp
>>> Using domain server:
>>> Name: ns1.isp
>>> Address: ns1.isp#53
>>> Aliases:
>>>
>>> Host 187.255.85.209.in-addr.arpa not found: 3(NXDOMAIN)
>>> [root at linux ~]# host 209.85.255.187 ns1.isp
>>> Using domain server:
>>> Name: ns1.isp
>>> Address: ns1.isp#53
>>> Aliases:
>>>
>>> Host 187.255.85.209.in-addr.arpa not found: 3(NXDOMAIN)
>>>       
>> Use 'dig -x 209.85.255.187 @ns1.isp' and look at "NS" records and TTLs.
>> Invalid delegations and inconsistent NS records (domain is delegated from
>> parent to different servers than those listed in the domain) often cause
>> these kinds of problems.
>>
>>     
> I think I did have same problem
> with 9.4.1p1, 9.5p2 and 9.6p1. Look
>
> [dieu at brandmauer ~]$ host www.bbc.co.uk 127.0.0.1
> Using domain server:
> Name: 127.0.0.1
> Address: 127.0.0.1#53
> Aliases:
>
> www.bbc.co.uk is an alias for www.bbc.net.uk.
> www.bbc.net.uk has address 212.58.253.68
> Host www.bbc.net.uk not found: 2(SERVFAIL)
> [dieu at brandmauer ~]$
>
>   
By default, "host" looks up A, AAAA and MX records, in that order.
> I did sniff connecction and It seems that the query that fails is a MX request 
> of www.bbc.net.mx. Odd thing.
>
>   
The delegated nameservers for bbc.net.uk are answering an MX query with 
an A record:

$ dig www.bbc.net.uk mx @ns0.rbsov.bbc.co.uk +short
212.58.253.68
$ dig www.bbc.net.uk mx @ns0.thdo.bbc.co.uk +short         
212.58.253.68

Really bad stuff, but this is a *persistent* condition, caused by the 
domain owner(s), and probably not related to the issue reported by the 
previous poster.

                                                                   - Kevin










More information about the bind-users mailing list