On Sun, Jun 5, 2011 at 16:06, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
I use the following line to get my current external IP in conky. Recently Its been hanging for ages before responding, so I tried it out and it seems to try an ipv6 address first before timing out and succeeding on the ipv4 address. I know I can just disable ipv6, but since on June 8th (AFAICR) there's gonna be a large scale test of that on the interwebz, probably a good thing to keep around. Any suggestions what the problem could be? Is it simply a faulty DNS server (I'm using my local ISP's DNS)?
wget -O -i icanhazip.com --2011-06-05 18:28:04-- http://icanhazip.com/ Resolving icanhazip.com... 2001:470:1f10:d57:feed:beef:cafe:d00d, 50.56.84.181 Connecting to icanhazip.com|2001:470:1f10:d57:feed:beef:cafe:d00d|:80... failed: Connection timed out. Connecting to icanhazip.com|50.56.84.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 16 [text/plain] Saving to: “-i”
100%[====================================================================================================================>] 16 --.-K/s in 0s
I had the same problem and i disabled ipv6. If the ipv6 module is not loaded and no ipv6 dns are defined (see http://www.chaz6.com/files/resolv.conf for a list of public ipv6 dns addresses), then you won't get this problem. The June 8th IPv6 test is for the same reason, browsers trying ipv6 address (till time-out) before fall-back to IPv4 address (if ipv6 module is loaded). Or you can use a IPv6 tunnel broker like freenet6 or Hurricane Electric and enable ipv6 module and ipv6 dns. Regards. Keshav