OPNsense Forum
Archive => 19.1 Legacy Series => Topic started by: brandon3055 on April 08, 2019, 10:21:53 am
-
I suspect i am overlooking something simple here but so far nothing i have found online has helped with this.
Im talking about mapping something like nas.lnet to a lan address like 192.168.1.133 so i can then use nas.lnet to access my nas web interface.
I only just switched to opnsense last night. Before that i was using pfsense. The way i had pfsense setup all i had to do was add a static mapping with a host and domain name to the DHCP server and it just worked. But i had been using that install for several years so i dont recall what i had to do to get that working.
So far in opnsense i have set host and domain name under System/settings/general and i have added a static entry with a host and domain name in Services/DHCPv4/LAN.
I also tried fiddling with Unbound DNS and OpenDNS but i'm not familiar with ether of those.
So. My question is. From a fresh opnsense install what steps would i have to take to get LAN DNS entries working?
-
you might talk from name resolution of your ips.
You will find this in unbound, bridging. Add a hostname and the appropriate IP of the host there.
-
I dont see bridging in unbound settings. (Services/Unbound DNS/???) Im guessing you may mean Overrides? If thats the case i have tried that but it does not seem to work. (https://ss.brandon3055.com/3ba89)
-
I managed to accomplish this by enabling 'Register DHCP static mappings ' under 'Unbound DNS->General'.
Caveat: I'm new to opnsense too
HTH
-
Ok... So mega facepalm...
Turns out when i removed my static DNS mappings to 1.1.1.1 and 8.8.8.8 on my Linux Desktop i didnt actually reset the connection so my system was still contacting cloudflare directly for DNS lookup.