Strange resolver behavior
Xin LI
delphij at delphij.net
Tue Feb 12 17:32:12 PST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
It looks like that certain (mis)configuration by the baidu.com DNS
administrators has caused this, but I have no clue why our resolver
would return NXDOMAIN after it gets a positive response? (Yes, I know
that _ is not appropriate for domain names :)
[delphij at charlie] ~> host -a dict.baidu.com
Trying "dict.baidu.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59711
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; QUESTION SECTION:
;dict.baidu.com. IN ANY
;; ANSWER SECTION:
dict.baidu.com. 7153 IN CNAME ps_other.a.shifen.com.
;; AUTHORITY SECTION:
baidu.com. 159107 IN NS ns4.baidu.com.
baidu.com. 159107 IN NS ns2.baidu.com.
baidu.com. 159107 IN NS ns3.baidu.com.
baidu.com. 159107 IN NS dns.baidu.com.
Received 136 bytes from 127.0.0.1#53 in 31 ms
[delphij at charlie] ~> host -a ps_other.a.shifen.com
Trying "ps_other.a.shifen.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64825
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; QUESTION SECTION:
;ps_other.a.shifen.com. IN ANY
;; ANSWER SECTION:
ps_other.a.shifen.com. 1113 IN A 202.108.22.46
;; AUTHORITY SECTION:
a.shifen.com. 72679 IN NS ns3.a.shifen.com.
a.shifen.com. 72679 IN NS ns2.a.shifen.com.
a.shifen.com. 72679 IN NS ns4.a.shifen.com.
a.shifen.com. 72679 IN NS ns1.a.shifen.com.
Received 127 bytes from 127.0.0.1#53 in 0 ms
[delphij at charlie] ~> host ps_other.a.shifen.com
ps_other.a.shifen.com has address 202.108.22.46
Host ps_other.a.shifen.com not found: 3(NXDOMAIN)
Cheers,
- --
Xin LI <delphij at delphij.net> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFHskiNi+vbBBjt66ARAhO0AKCI64gr+oNw7j8/TcL51b7vw1PReQCeMRE1
RaI38+YYtloZuSc0L0BDF2M=
=ONkQ
-----END PGP SIGNATURE-----
More information about the freebsd-net
mailing list