Re: IPv6 et résolution Bind

On Thu, Jun 09, 2011 at 09:32:39AM +0200,
 Firebolt <[email protected]> wrote 
 a message of 23 lines which said:

> DNS format error from 74.54.83.122#53 resolving probag.net/AAAA for
> client 127.0.0.1#43582: invalid response

BIND a raison, leurs serveurs ne répondent pas correctement aux
requêtes AAAA.

% dig AAAA probag.net

; <<>> DiG 9.7.1-P2 <<>> AAAA probag.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 52364
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;probag.net.			IN	AAAA

;; Query time: 272 msec
;; SERVER: 148.60.80.251#53(148.60.80.251)
;; WHEN: Thu Jun  9 10:05:32 2011
;; MSG SIZE  rcvd: 39


% dig A probag.net

; <<>> DiG 9.7.1-P2 <<>> A probag.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47320
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;probag.net.			IN	A

;; ANSWER SECTION:
probag.net.		3577	IN	A	74.54.82.222

;; AUTHORITY SECTION:
probag.net.		172773	IN	NS	ns2.expireddomains.register.com.
probag.net.		172773	IN	NS	ns1.expireddomains.register.com.

;; ADDITIONAL SECTION:
ns1.expireddomains.register.com. 34 IN	A	74.54.82.122
ns2.expireddomains.register.com. 34 IN	A	74.54.83.122

;; Query time: 3 msec
;; SERVER: 148.60.80.251#53(148.60.80.251)
;; WHEN: Thu Jun  9 10:05:39 2011
;; MSG SIZE  rcvd: 150


> DNS format error from 150.128.197.37#53 resolving marti.uji.es/AAAA:
> invalid response

Idem.

> Si vous avez une piste sur ces messages :(

Il y a beaucoup de neuneus qui gèrent un serveur DNS.