Quote:
Originally Posted by DutchDaemon
Other than that, seems your ISP (Wanadoo/IP2000) uses a rather weird network setup, involving two/three RFC1918 networks.
What you could try (if you have your own nameserver) is to forward all DNS requests to your ISP's nameservers. The fact that you get a quick reply to www.sun.com is probably because that result is already cached as a result of your earlier visit to that site. Try a dig on some host you've never visited, and see what the response time is to that query. Then try with your DNS requests forwarded to your ISP's nameservers. If you have a lot of latency on your network, a typical external DNS lookup (non-forwarded), which can involve a lot of questions and answers (sometimes more than ten separate queries), suffers a lot. |
DNS queries works with any domain name.
Like :
Code:
[mururoa@mururoa2 /usr/home/mururoa]$ dig +search www.ibm.com
; <<>> DiG 9.4.2 <<>> +search www.ibm.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28408
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.ibm.com. IN A
;; ANSWER SECTION:
www.ibm.com. 3575 IN CNAME www.ibm.com.cs186.net.
www.ibm.com.cs186.net. 35 IN A 129.42.56.216
;; Query time: 76 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Thu Oct 23 13:05:30 2008
;; MSG SIZE rcvd: 80
That works with any query.
I dont have a real DNS just a dns cache on my router.