NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
tomsliwowski
Mar 22, 2018Apprentice
Orbi Local DNS?
So I have a number of systems that I've assigned static DHCP addresses and I was wondering if the Orbi has some local DNS server that I can configure to resolve them? I have a file server, a Plex...
FURRYe38
Aug 29, 2018Guru - Experienced User
Yes for average or un-experienced users I would also not recommend doing this to the router.
So after you get into telnet, what is the next step, how do you edit the .conf file in VI? Is the file downloaded to the PC, edited then re-uploaded or edited live on the router thru VI?
Yes, hacy work around and not much information to go in is reason for asking questions. If some users are wanting to try this, then it would be nice to have exact steps. :smileywink:
tomsliwowski wrote:
Vi is usually installed as one of the basic utilities in a *nix system. There are tons of tutorials out there on how to use it but honestly I suggest you play around in something like Ubuntu before messing with any files on you router.
As for how you get to the file, first you need to enable telnet on the router. Go to http://orbilogin.com/debug.htm and check off the "Enable Telnet" option. Then just telnet to your router IP and log in using your admin credentials (I think).
The hacky workaround mvdp linked to would work but since the config file is in /tmp I believe it won't survive a reboot of the router.
tomsliwowski
Aug 29, 2018Apprentice
You would edit the file live on the router. Basically you're telling dnsmasq that you want to use an additional file in the same format as /etc/hosts (that's what the line addn-hosts=/tmp/dhcpd_hostlist means)
So once you add that to /tmp/resolv.conf you need to create a new file called /tmp/dhcpd_hostlist and put in entries for earch device you want to use a hostname for in the format
IP hostname
So for me it would say something like
192.168.254.118 Sickrage
192.168.254.45 OctoPi
Then you kill the running dnsmasq and reload the newly modified version:
kill $(pidof dnsmasq)
/usr/sbin/dnsmasq --except-interface=lo -r /tmp/resolv.conf
Hopefully both the monification to resolv.conf and the new dhcpd_hostlist file survive a reboot but honestly I don't know if they will