Chris Green
2017-03-03 15:49:59 UTC
In Ubuntu systems (and maybe debian, not sure about this) dnsmasq is
run my NetworkManager to provide local DNS, the process shows up as:-
nobody 1470 1022 0 15:01 ? 00:00:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
Is there any easy way to get it to recognise some local names? I have
(in particular) a BeagleBone black on one LAN I use and it would be
really handy to be able to call it 'odin' rather than have to find its
IP address every time.
DHCP for the LAN is provided by a router which, sadly, doesn't seem to
know about local names.
Ideally 'odin' should only be present when it actually *is* present
(i.e. when I'm connected to the specific LAN where it exists), but
this isn't absolutely necessary.
run my NetworkManager to provide local DNS, the process shows up as:-
nobody 1470 1022 0 15:01 ? 00:00:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
Is there any easy way to get it to recognise some local names? I have
(in particular) a BeagleBone black on one LAN I use and it would be
really handy to be able to call it 'odin' rather than have to find its
IP address every time.
DHCP for the LAN is provided by a router which, sadly, doesn't seem to
know about local names.
Ideally 'odin' should only be present when it actually *is* present
(i.e. when I'm connected to the specific LAN where it exists), but
this isn't absolutely necessary.
--
Chris Green
Chris Green