what are the meanings of these errors ?

[Kevin Darcy]

高冲 wrote:
> the following erros are shown in the named.log.
> what are these meanings ?
>
>  
>
> thanks .
>
>  
>
> 25-Jul-2008 12:22:19.544 unexpected RCODE (SERVFAIL) resolving
> 't1.dvd88.cn/A/IN': 60.191.110.158#53
>   
Remote nameserver gave back a SERVFAIL error for this query. It is now 
responding normally, as far as I can tell.
>  
>
> 25-Jul-2008 12:27:31.352 unexpected RCODE (REFUSED) resolving
> 'dns2-ftcg.gdsz.cncnet.net/AAAA/IN': 210.21.196.6#53
>   
Remote nameserver gave back a REFUSED error for this query. In fact, 
both of the delegated nameservers for the domain -- this one and 
210.21.220.6 -- are giving REFUSED, so the domain is totally unresolvable.
>
> 25-Jul-2008 12:37:02.944 unexpected end of input resolving
> 'squidclick.bbs.tianya.cn/AAAA/IN': 221.11.172.10#53
>   

Response packet from a remote nameserver was malformed.

I can reproduce this issue also. It's actually putting a record of type 
AAAA in the Answer Section, but the RDLENGTH is set to 0 (AAAA records 
are supposed to have a fixed 16-byte RDATA). The nameserver is also 
trying to include all 13 root NS records in the Authority Section, which 
is odd since it's authoritative for the closest-enclosing domain 
(bbs.tianya.cn). It's seriously confused.

>  
>
> 25-Jul-2008 12:22:19.701 lame server resolving 'bbs.huangshan.gov.cn' (in
> 'huangshan.gov.cn'?): 202.102.128.69#53
>   
A remote nameserver that was delegated a particular zone 
(huangshan.gov.cn), turned out to not be authoritative for it. Otherwise 
known as "lame".

I note that neither of the delegated nameservers for huangshan.gov.cn 
currently have the address listed above, so it appears they fixed the 
problem.
>
> 25-Jul-2008 12:27:31.482 FORMERR resolving 'pingfore.qq.com/AAAA/IN': 60.28.
> 234.10#53
>   
Remote nameserver gave a FORMERR (format error) response when trying to 
resolve a particular query. If the remote nameserver did not have 
support for the AAAA RR type, it should have responded with NOTIMP 
instead of FORMERR.

I cannot reproduce this problem -- pingfore.qq.com/AAAA gives a valid 
response from the 60.28.234.10 nameserver -- so it's possible this 
problem was fixed also. Or, possibly that nameserver is really a cluster 
and not all nodes in the cluster have a problem resolving AAAA queries.
>  
> 25-Jul-2008 12:27:30.586 client 219.82.45.219#1730: query:
> member1.taobao.com IN AAAA +
>
> 25-Jul-2008 12:27:30.588 client 218.108.199.10#530: query:
> huoju.icoke.qq.com IN A +
>
>   
Normal querylog entries, not errors.

- Kevin