Setting LAN DNS

[elineweaver]

Having an issue when setting LAN DNS for DHCP to my local PiHole server. I selected Disabled for Automatic DNS, set primary to what I want, have tried leaving secondary blank as well as inserting 0.0.0.0. Have also done a soft reboot and hard reboot. Devices on network still get the Netduma address as DNS.

[Netduma Fraser]

Hey, welcome to the forum!

 

Reboot from miscellaneous settings after having set the DNS you want then see if it has applied then.

[elineweaver]

I have done that but will try again.  For the Secondary DNS do I need to leave blank, use 0s, or put the same as the Primary?

[Netduma Fraser]

You don't need to put in a secondary DNS, could just go with 8.8.4.4 which is what I use.

[elineweaver]

Tried blank and with 8.8.8.8, rebooting like you said. Same thing. Also tried disabling ipv6 and then doing the above and same thing. Thanks.

[scbba]

Well the 8.8.8.8 is a primary it won't work in then secondary leave it blank or put 8.8.4.4

[elineweaver]

I have set local server as primary and 8.8.4.4 as secondary as DNS.  I then rebooted from MISC menu.  Then did a release/renew on two different workstations.  Still getting an IPv6 DNS entry and 192.168.88.1.

[elineweaver]

I gave up after trying a factory reset.  Moved DHCP back off the Netduma for now.

[Netduma Fraser]

I would imagine that it's slightly out of the scope of what it would normally be used for. If you set manual DNS on your devices to pihole server does that work?

[elineweaver]

Yes.  Problem is not with the PiHole or DNS.  Issue is with the DHCP Server setup on the NetDuma.  When I move DHCP to the PiHole or say a WAP or whatever it works fine.  The NetDuma will not hand out anything but 192.168.88.1 as the DNS server even after setting multiple different things under the LAN settings.  So for now I disabled DHCP on the Duma and moved it to a different device.  Not sure why the Duma DHCP server will not had out any manually set DNS in LAN settings.  I tried PiHole, Google, OpenDNS with just primary and with primary/secondary and it still hands out .1 as DNS server.

[nytemare01]

I noticed that too. No matter what I set the dns server too on lan (75.75.75.75 Comcast) the Duma still hands out 192.168.88.1 as the dns server

[PharmDawgg]

Giving out 192.168.88.1 as the dns server is ok.  What the console is doing is sending a dns request to the router and the router is sending the request on to the dns resolver beit google dns or opendns or your ips dns.  If you don't won't your device to say 192.168.88.1 under dns then you need change dns from automatic to manual on you console. Then the console with bypass the router make requests directly to google dns/opendns etc.