[themusj]

Is there a setting that keeps ,home.lan not resolving on my home internal lan.
Using .home.arpa does work and resolve to my internal IP. I am using Pi-hole for DNS, but not DHCP.

[SurprisedItWorks]

I happened to discover only today that if you are using dnsmasq (GUI>Services>Services), the Additional Option you'd need in Dnsmasq Infrastructure there is

[kernel-panic69]

[themusj]

Thank you and yes, the comma was typo for . period.

Added this: domain=home.lan,192.168.25.0/24,local to Additional Options and still getting Google Search results rather than hitting my Unraid server (Setup in Pi-hole as unraid.home.lan with associated IP of 192.168.25.155)

Rebooted router too.

[kernel-panic69]

Sounds like it's a piHole problem, not (necessarily) a DD-WRT problem. Need more info to determine for sure, but you should be ignoring WAN DNS on DD-WRT, not using any static DNS entries save and except maybe manually pointing to your chosen NTP server, and pointing dnsmasq on DD-WRT to your piHole.

[themusj]

One resource said to "Use Dnsmasq for DNS", and set Static DNS1 to the Pi-hole address.

Then under Services > Dnsmasq, add dhcp-opton=6, 192.168.1.281 in the Additional Dnsmasq options box. Where the IP is the Pi-hole address.

Didn't work. Still brought up Google Search results. So far just .arpa works.

I could turn pi-hole off and take that out of the equation.

If that is the case, do I fall back on the earlier suggestion? "domain=home.lan,192.168.1.0/24,local

[themusj]

Current status is I have unraid.home.lan in my Pi-hole local hosts DNS records and NSLookup resolves both by IP and Name.

My Pi-hole setup runs with Unbound so not sure if that factors into why typing in unraid.home.lan does not resolve locally instead of a Google Search.

I entered the following in DnsMasq on my DD-WRT router based on this link.

https://wiki.dd-wrt.com/wiki/index.php/DNSMasq_-_DNS_for_your_local_network_-_HOWTO

address=/unraid.home.lan/192.168.xxx.xxx
ptr-record=unraid,192.168.xxx.xxx

No success.

So odd that unraid.home.arpa works. There has to be a simple explanation.

My router is set with static IP address for each node under the DHCP settings.

[kernel-panic69]

Do you have expand-hosts set for dnsmasq? Because local DNS should still be queried by dnsmasq.

[themusj]

DD-WRT setup DHCP Server with Static DNS1 set to Pi-hole IP

All devices assigned static IP.

Use dnsmasq for DNS checked.

DHCP-Authoritative checked.

Enable Resolver checked

Pi-hole as Server set in Local DNS Records as unraid.home.lan with IP 192.168.xxx.xxx

Thank you for your insights to the problem.

[kernel-panic69]

Two presumptions based on your info:

1) Recursive DNS Resolving (Unbound) <-- "Enable Resolver"
2) All of your devices have a static LEASE <-- "All devices assigned static IP."

If you're using a pi-Hole, you probably don't need Unbound enabled, nor do you need dnsmasq for dns enabled:

use Pi-Hole as simple DNS-Server with DD-WRT

Sorry for my delay in connecting the dots.

[themusj]

At least you have the ability to connect the dots!

I tried setting the option 2 method in the link. Some options in Pi-hole I could not change and I assume that is because of Unbound being incorporated in the docker. I have two instances of Pi-hole running with unbound, with separate static IP addresses.

So of course it didn't work even flushing the dns and trying Chrome besides Firefox.

I even tried the video below which made it look so easy. Followed every step except for the certificate (which I have been working on). Still with nextcloud.home.lan I ended up on the Internet.

https://www.youtube.com/watch?v=hS76TQO0A8s

I know unbound does some upstream processes so if I delete both Pi-hole dockers with Unbound and re-install them, what am I going to lose? I am working on self-signed certificates for Nginx so my home lan no longer has those browser warnings. Somehow I have made this more complicated than I think it is or otherwise it is.

[themusj]

Well this may not be the way it is supposed to be done, but it does work.


I can type unraid.home.lan or nextcloud.home.lan in Firefox and it is working now.

Apparently Firefox did not recognize .lan in the whitelist without an edit to the config file.


Method 2: Firefox about:config (For home.lan specifically)

This helps Firefox recognize .lan as a local domain for internal lookups.

-Type about:config in the Firefox address bar and press Enter.

-Accept the risk if prompted.

-Search for browser.fixup.domainsuffixwhitelist.lan.

-If it doesn't exist, create it as a Boolean (click the + sign) and set the value to true.

Pi-hole > Nginx > DD-WRT router. I assume Chrome must have some way to edit it as well.

[themusj]

Thank you all for you help and insights. I was able to get this resolved, after literally months of on again off again work.

I love dd-wrt and the forum. The solution turned out to be a long list of things to make this work both as an internal dns server, and resolving my ssl issues.

Again, I appreciate everyone's assistance.!