Nick Rout wrote: > On Thu, 01 Jun 2006 15:28:19 +1200 > David Kirk <[EMAIL PROTECTED]> wrote: > > >> Roger, >> >> >>> don't want to do that. My (possibly invalid) assumption was that name >>> resolution is being provided by the router as the other (windows) >>> machines are able to resolve names OK (given the successful pings by >>> names from them) but for some reason this linux box isn't getting that? >>> Could be I'm demonstrating a clear lack of understanding of the process >>> here... >>> >> DHCP assigns IP addresses to network hosts. It can be configured to >> hook in to DNS, but I doubt that would be the case in a router. >> >> More likely is that your Windows boxes are using NetBIOS to resolve host >> names. >> >> -- >> Later >> >> David Kirk >> > > or it could be that the search line in /etc/resolv.conf needs tweaking. > dns is great when it just works, but a pita otherwise. > > one way to get it to work is to use dnsmasq on the dhcop server. > dnsmasq is a very simple dns proxy that also resolves local addresses > from /etc/hosts and the dhcp.leases file. Anything it cannot resolve > locally it passes off to an external server, probably your ISP's. > > Of course you need to run it on the dhcp box, ie turn all that stuff > off on the router and do it from an always on linux box. > hmmm... the router is pretty simple and it's only dns settings relate to the wan. there is no dns or dhcp server box on this network.
I'm surprised that it looks like I'm stuck at this point, I thought that there would be some piece of linux magic that can allow this box to resolve the IP address from name in this common enough scenario (smallish network with simple dhcp router that is NOT a dns server). Looks for now like I'll have to carry on looking up the address of a machine from the router's table of dhcp clients . . . Cheers for all the replies anyway. Roger
