Unable to use local DNS records set in Pi-hole ONLY on my PC

Hello.

I’m unable to enter websites using DNS records set in my Pi-hole. I can connect using IP and this only happens on my EndeavourOS PC. I have tested it with on my phone and it works there, also tried different browsers, same result.

Example:
router.local is assigned to 192.168.0.1
entering 192.168.0.1 directs me to the router page
entering router.local gives “ERR_NAME_NOT_RESOLVED”

The tricky thing is:

running nslookup router.local

Server: 192.168.0.10
Address: 192.168.0.10#53

Name: router.local
Address: 192.168.0.1

So the computer does resolve the address, but doesn’t in the browser?
Another thing is, the pi.hole works fine.

My phone, PC, router and the machine with Pi-hole are all on the same subnet, so this has to be a problem with my computer.

All help welcome :slight_smile:

Which browsers? I think about 80% of the browsers I use all have DOH turned on by default so they bypass your local DNS unless you disable that.

Firefox, Brave, LibreWolf and Vivaldi.

Checked in LibreWolf settings, DOH is disabled.

All of those have DoH on by default.

If nslookup is returning the correct result and your browser isn’t it seems like it is most likely an issue/setting with your browsers.

Do you know a browser that doesn’t to check if that works?

If DNS Over HTTPS is disabled, what else could be causing this?

P.S. On my phone I have DNS Over HTTPS set to “Default Protection”.

falkon

Tried falcon, same result.

Also tested LibreWolf on windows, same PC, works there aswell.

Also Lynx and links :wink:

core/links 2.30-1
A text WWW browser, similar to Lynx
extra/lynx 2.9.2-2
A text browser for the World Wide Web

Can you reach it with router.local.? Note the additional dot at the ending.

Nope

There are two main issues.

#1 browsers usually have a build in list of valid top level domains, so everything else is considered a search term. In Firefox you can circumvent it by making it a fully qualified top level domain by adding a dot to the address - no clue about other browsers.

#2 .local is esp. bad though, because that is somewhat even more special involving mDNS. A little bit more on it here. #1 for .local doesn’t work in FF either.

Are you committed to .local? I did a quick test with my pi-hole and .home or .lan works in FF with router.home. or router.lan..

2 Likes

router.home. does work in Firefox and LibreWolf, many thanks. It doesn’t however work in Brave and Vivaldi, the browser searches for it instead. Adding http(s):// fixes that, probably a chromium thing.

I may just go for a more obscure and not taken domain ending with .net or similar as that works on all of the browsers. Adding a dot at the end may feel weird for users.

Thank you so much for the help!

1 Like