On Thu, May 01, 2014 at 12:57:44AM +0100, steve-ALUG@hst.me.uk wrote:
A DHCP server (Dynamic Host Configuration Protocol) basically just doles out IP addresses and maintains a list of who asked for it when. This is tied up with MAC addresses.
A DNS (Domain Name System) server is the thing that works out what things are called within your LAN. If your devices are named, then it will associate names with IP addresses and allow you to connect by name rather than IP address.
Yes, I know that (I do run dnsmasq at home to do both these things), what I want to know is how one deals with the reality of what happens with the 99% of domestic routers nowadays that don't seem to provide local DNS.
Your WIFI router will be running a DHCP server, but is almost certainly NOT running a DNS server for your LAN. This is why your
They used to once upon a time, most 'early' ADSL routers *were* local DNS servers as well. I have a couple of old ones that do this.
If you can't get internal DNS on your router, you need to run a DNS server somewhere. For this you need a device that's on all the time. Presumably your Beaglebone Black is. Hopefully there's a
Yes, running dnsmasq on the BBB is a possibility, but I still don't understand how the non-techie sort of person is supposed to deal with 2 printers, a Siemens Gigaset, a NAS backup, etc. on their home network.
It was more of a rant than a request for help - sorry! :-)