> OK, well I am pretty much out of ideas. You could try plugging it into a > hub (not a switch, just a cheap nasty hub) and using another computer on > the hub running wireshark to figure out at the packet level what sort of > DNS queries it is doing. It may come to that yet... but in the mean time...
Further tinkering shows that exporting the http_proxy setting for the upstream proxy server export http_proxy=194.66.xxx.yyy:8080 makes WGET work without the -4 option... but it has no effect on general DNS resolution.. Trying out dig with its -4 option still doesn't work... --------------------------------------------------------- ad...@proxy:~$ dig sky.com -4 ; <<>> DiG 9.4.2 <<>> sky.com -4 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 42955 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;sky.com. IN A ;; Query time: 1015 msec ;; SERVER: 10.82.xxx.yyy#53(10.82.xxx.yyy) ;; WHEN: Sun Mar 29 21:30:44 2009 ;; MSG SIZE rcvd: 25 ---------------------------------------------------------- Interestingly, the DNS server being used is the internal Windows DNS server, which is listed third in the resolv.conf after the two entries for OpenDNS's server, so I'm not sure what's going on there... I can ping the OpenDNS servers by their IP addresses and that works fine... I think I'm starting to get a headache.... Lee -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
