Re: bind-9.7.2 not forward CNAMEDed domain names

2011-02-22 Thread Drunkard Zhang
2011/2/22 Florian Weimer : > * Drunkard Zhang: > >> My capture command: tcpdump -s 0 -nnnvvv -w 360.cn-`date +%Y%m%d`.pcap >> udp port 53 >> >> 17:59:36 ~ $ dig +nocmd speedtest.360.cn @211.161.192.1 +multiline >> +noall +answer >> speedtest.360.cn.     215 IN CNAME speedtest.360.cn.cloudcdn.net. >

Re: bind-9.7.2 not forward CNAMEDed domain names

2011-02-22 Thread Florian Weimer
* Drunkard Zhang: > My capture command: tcpdump -s 0 -nnnvvv -w 360.cn-`date +%Y%m%d`.pcap > udp port 53 > > 17:59:36 ~ $ dig +nocmd speedtest.360.cn @211.161.192.1 +multiline > +noall +answer > speedtest.360.cn. 215 IN CNAME speedtest.360.cn.cloudcdn.net. > speedtest.360.cn.cloudcdn.net. 325

Re: bind-9.7.2 not forward CNAMEDed domain names

2011-02-22 Thread Drunkard Zhang
The upstream DNS server 211.161.192.1 did responsed correctly, by analysis via tcpdump.  But why bind didn't use THE RESPONSE, but resolves again from root-servers. >>> >>> Unfortunately, the information provided by 211.161.192.1 must be >>> discarded because that is server is not au

Re: bind-9.7.2 not forward CNAMEDed domain names

2011-02-22 Thread Florian Weimer
* Drunkard Zhang: > 2011/2/22 Florian Weimer : >> * Drunkard Zhang: >> >>> The upstream DNS server 211.161.192.1 did responsed correctly, by >>> analysis via tcpdump.  But why bind didn't use THE RESPONSE, but >>> resolves again from root-servers. >> >> Unfortunately, the information provided by 2

Re: bind-9.7.2 not forward CNAMEDed domain names

2011-02-22 Thread Drunkard Zhang
2011/2/22 Florian Weimer : > * Drunkard Zhang: > >> The upstream DNS server 211.161.192.1 did responsed correctly, by >> analysis via tcpdump.  But why bind didn't use THE RESPONSE, but >> resolves again from root-servers. > > Unfortunately, the information provided by 211.161.192.1 must be > disca

Re: bind-9.7.2 not forward CNAMEDed domain names

2011-02-22 Thread Florian Weimer
* Drunkard Zhang: > The upstream DNS server 211.161.192.1 did responsed correctly, by > analysis via tcpdump. But why bind didn't use THE RESPONSE, but > resolves again from root-servers. Unfortunately, the information provided by 211.161.192.1 must be discarded because that is server is not aut

bind-9.7.2 not forward CNAMEDed domain names

2011-02-22 Thread Drunkard Zhang
I just add these in default named.conf: zone "speedtest.360.cn" { type forward; forwarders { 211.161.192.1; }; }; which reacts like this: 17:20:09 ~ $ dig +nocmd speedtest.360.cn @211.161.192.146 +multiline +noall +answer speedtest.360.cn. 34 IN CNAME speedtest.360.cn.cloud