I’ve been fooling around a bit with my network, just trying to understand how some things work (this is an area I’m pretty clueless in). I have a Linksys WRT54G router, and I’m running the Sveasoft Firmware (2.00.8sv). This firmware apparently enables DNSMasq by default, and I’ve checked that it’s marked enabled in the web interface.

DNSMasq is a combination DHCP server and lightweight DNS server, designed to handle DNS for local machines on your network. It’s supposed to handle name resolution for the DHCP clients on your network that supply machine names. By viewing the DHCP clients table via the web interface, I can see that all my machines are reporting names to the DHCP server.

In spite of this, I (mostly) cannot get name resolution on my local network. The two Windows machines on the network (both wired, incidently) can ping each other by name, but can’t ping other machines. Other machines on the network can’t ping any local machines. I suspect the windows machines are cheating (via WINS?). Running NSLookup shows that each machine is using my ISP’s DNS server directly, not the router. I’m not sure if that’s how it should work or not. Directing NSLookup to talk to the router directly yield no results for any local machine name.

So I’m stuck. I’ve googled a bit, and looked around Sveasoft’s forums. I kinda have the impression it should Just Work. If anyone has any knowledge to share, I’d be greatful.

Both comments and pings are currently closed.

3 Responses to “DN(Clueles)S”

  1. Hinoserm Says:

    I had a similar issue, and eventually figured out that DNSMasq works only if and only on any static DHCP entries you define under the “Enable DHCP” options right above DNSMasq. I think you also need to make sure you have “domain name” filled in on the Setup page.


  2. Hinoserm Says:

    Actually, no. Now that I’ve set domain name, it works fine with all the DHCP entries. If you want the WRT54G to automatically give out itself as a DNS server when machines make DNS requests, stick it’s (internal) IP address in one of the “Static DNS” fields on the Setup page.


  3. Scott Hanselman Says:

    I had this problem forever, and when I set the domain name it was fine.