maemo.org - Talk - View Single Post - Name resolution not working on n810

	fattomm	2008-12-06 , 17:24
	Posts: 109 \| Thanked: 37 times \| Joined on Oct 2008 @ NYC, NY	#2

Originally Posted by stevecrye

Hi All;

Name resolution seems to be the only thing that is broken, and it is broken regardless of the app that is trying to do the resolution. If I run nslookup and specify a name host and nameserver, I get a good result. I can ping and traceroute OK if I know the destination IP, and I can browse to sites if I know the IP -for example, my Linksys router's html config screens.

[...]
ifconfig does not seem to list the DNS, (even when run while booted to the working flash partition). I'm not certain how to do the equivalent of the Windoze ipconfig /all. Does anyone know the correct utility to run to confirm that the NIT has been given a valid IP of a nameserver? Also, what process/daemon is responsible for name resolution? Named?

Tried searching the forums for "can't resolve names" and similar but no luck.

Any and all hand-holding much appreciated!

Thanks,

$teve

I think I had something like this some time ago. nslookup, by the way, doesn't use the system resolver configuration.

The NIT uses "dnsmasq", which I don't like much, but is reasonable given the approaches the system takes. Check your /etc/resolv.conf file, and it should have (at least)

nameserver 127.0.0.1

in it. I've added my local domain name, which made life a lot easier. The system resolver libraries read this file, and send DNS requests to the 127.0.0.1 (localhost) server - which is dnsmasq. dnsmasq is ultimately configured to read the file /tmp/resolv.conf.<interface name> -- you should see a /tmp/resolve.conf.wlan0 when your wireless is running.

If your DHCP served up by your wireless router isn't passing over good information (as configured from there, or from whatever DHCP server you're using), then you'll see the shortcomings in this file.

I manually put a "search <myowndomain>" in my /etc/resolve.conf file, since the /tmp/resolve.conf.wlan0 is going to have information from whatever access point I'm tethered to. The "search" in the local file allows me to use short-hand names for my own home systems even when I'm using public access points, friends', or whatever ... (or bluetooth links to my phone).

In short; for default types of parameters you want regardless of your connectivity model, look at /etc/resolv.conf. For specifics passed in via various connection means, look at /tmp/resolve.conf.<interface name>.

I think that should clear things up a bit for you. Broken DNS can be a PITA ...

Quote & Reply |

The Following User Says Thank You to fattomm For This Useful Post:
fixerdave