LAN-side DNS Server
-
The Amplifi HD already allows me to apply custom names to each device that is connected to it. It would be nice if the router could act as an internal DNS server of my LAN devices' IPs so that I can interact with other devices on my LAN with their hostnames instead of having to know their DHCP-assigned IP addresses.
-
@shawn-riley It does as long as your using the router as your DNS server. The domain is '.lan'.
C:\Users\mreck>nslookup
Default Server: pihole-2
Address: 2001:470:xxxx:xxxx:xxxx:2! Changing to router as my DNS server since I use a different one by default.
server 192.168.180.1
Default Server: [192.168.180.1]
Address: 192.168.180.1! Checking reverse lookup
192.168.180.244
Server: [192.168.180.1]
Address: 192.168.180.1Name: amazon-75dc10304.lan
Address: 192.168.180.244! Checking forward lookup
amazon-75dc10304.lan
Server: [192.168.180.1]
Address: 192.168.180.1Name: amazon-75dc10304.lan
Address: 192.168.180.244
-
@michael-eckhoff This makes complete sense actually, the router has to have some way to internally look up and dispatch requests for internal resources.
Obviously it’s worth mentioning that if you run your own internal DNS servers, none of this will work unless you create a custom zone. Great response though.
-
@jayson-knight yes, if you run your own you have to setup a delegation for lan and your reverse in-addr.arpa domain. I have another post that explains how to do that with dnsmasq (search for pi-hole if needed).
-
I came here to request local DNS, and was delighted to see this thread with the .lan solution. However, it isn't working for me; none of my wired or wireless static leases show up via .lan, except for two wireless iMacs with static leases.
Not doing anything fancy here, just a handful of static wired and wireless leases. Any suggestions?
-
After letting it sit overnight, the .lan addresses are working. I must have had a cache issue, Ignore me and my lack of patience.