Quoting Per Jessen
Jeffrey L. Taylor wrote:
Quoting Per Jessen
: Jeffrey L. Taylor wrote:
While traveling, I found a motel with WiFi where Firefox and the DNS utilities, nslookup and dig, worked as expected, but wget, termtter (a CLI Twitter client), my Ruby on Rails applications, and several other programs could not resolve any domain names (getaddrinfo error, from memory). If I plugged the IP address obtained with nslookup into /etc/hosts, they worked as expected.
Could anyone enlighten me about how these programs resolve domain names differently?
Basically they don't - apart from nslookup and dig, they would use getaddrinfo() (or the equivalent) and that's it. I don't understand how firefox could work when the others failed, but it's probably worth double checking your /etc/resolv.conf
IIRC, Firefox does it's own lookup. I've forgotten how I found this out and what tipped me off. /etc/resolv.conf looks reasonable, nameserver and search lines.
And /etc/nsswitch.conf ?
dated 2010-01-27 passwd: compat group: compat hosts: files dns networks: files dns services: files protocols: files rpc: files ethers: files netmasks: files netgroup: files nis publickey: files bootparams: files automount: files nis aliases: files
Something is wrong with your resolver setup, that's where you need to look.
Only with the one wireless access point. I probably won't use it again until August. If it is still a problem at that time, I'll fire up Wireshark and try and see what the difference is at the network level. Thanks, Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org