In general, you can find a suitable DNS server as your own DNS resolution server, but if you choose improperly, it may lead to network selection is not optimal.
This situation generally occurs in the domain name optimized by telecom Netcom.
Check method (the domain name has been replaced):
[Email protected] ~]# dig cdl.cdn.aslibra.com
... Omitted
;; ANSWER section:
cdl.cdn.aslibra.com. 683 in A 218.25.68.145
cdl.cdn.aslibra.com. 683 in A 218.25.68.192
cdl.cdn.aslibra.com. 683 in A 218.25.11.105
;; Query Time:6 msec
;; server:202.106.0.20#53 (202.106.0.20)
;; when:wed June 10 16:40:07 2009
;; MSG SIZE rcvd:84
[Email protected] ~]# dig cdl.cdn.aslibra.com +trace
... Omitted
cdl.cdn.aslibra.com. 60.191.185.162 in A
cdl.cdn.aslibra.com. 60.191.187.8 in A
... Omitted
;; Received 282 bytes from 61.160.207.67#53 (ns1.dnspod.net) in 0 ms
The first one is the current own network, dig +trace is to use their own to get the parse
We see that the first and second time is not the same, the reason is relatively simple, this is the different lines of netcom and telecommunications
The first is returned from the 202.106.0.20 (own DNS server), with its access to the target domain name server obtained by the data, that is, if it is the Netcom IP, then return is the resolution of the Netcom, and trace directly consult the target domain name server, the target server based on your IP to return the resolution scheme.
If you are a telecommunications line, and set is the DNS server Netcom line, this time it is easy to obtain the solution of Netcom.
Also give us some attention to the place:
1 Setting up your own local DNS cache server is the most appropriate resolution solution
2 The DNS server that finds its own line has the best access effect
Pay attention to your own DNS settings-Aquan's Den