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. Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

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

Per Jessen wrote:

Jeffrey L. Taylor wrote:

...

...

And /etc/nsswitch.conf ?

[snip -looks good]

...

Something is wrong with your resolver setup, that's where you need to look.

Only with the one wireless access point.

Then we need to know what it looks like when you're connected via that access point - I'm guessing you've got dhcp changing /etc/resolv.conf for you, otherwise there is no reason why it would be any different.

Uh, another possibility is that the nameservers listed in /etc/resolv.conf are only accessible from certain networks. When you then connect via a different network (your otel with wifi), access is denied. Which nameservers do you currently have in /etc/resolv.conf? -- Per Jessen, Zürich (5.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jeffrey L. Taylor wrote:

...

Uh, another possibility is that the nameservers listed in /etc/resolv.conf are only accessible from certain networks. When you then connect via a different network (your otel with wifi), access is denied. Which nameservers do you currently have in /etc/resolv.conf?

/etc/resolv.conf is fully replaced by dhcp for each access point. Remember, Firefox, nslookup, and dig all work fine.

Yes, but like you said - firefox does it's own resolving, and so does nslookup and dig.

It is only some programs like wget that cannot resolve addresses.

There has got to be something wrong with /etc/resolv.conf or the access to the servers it refers to. -- Per Jessen, Zürich (9.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jeffrey L. Taylor wrote:

Quoting Per Jessen :

...

Jeffrey L. Taylor wrote:

...

...

Uh, another possibility is that the nameservers listed in /etc/resolv.conf are only accessible from certain networks. When you then connect via a different network (your otel with wifi), access is denied. Which nameservers do you currently have in /etc/resolv.conf?

/etc/resolv.conf is fully replaced by dhcp for each access point. Remember, Firefox, nslookup, and dig all work fine.

Yes, but like you said - firefox does it's own resolving, and so does nslookup and dig.

...

It is only some programs like wget that cannot resolve addresses.

There has got to be something wrong with /etc/resolv.conf or the access to the servers it refers to.

nslookup and dig are using the DNS server /etc/resolv.conf refers to.

Yes, but they do not use getaddrinfo(), which is the regular interface to the resolver. Okay, I'm not sure about nslookup, but dig certainly makes up its own UDP queries. -- Per Jessen, Zürich (8.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hans Witvliet wrote:

how about doing an /etc/rc.d/nscd restart Something might be lingering in your cache..

That wouldn't stop new queries being answered though. -- Per Jessen, Zürich (6.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org