[SOLVED] Firefox and local dns host names
[SOLVED] replaced router (for another reason) and new model works fine somehow
Hey guys, my Firefox on Android cant open selfhosted services using DNS host names on home wifi.
I moved to a new place, got new router, configured server with new local IP. On PC everything works fine, but on Android Firefox I get "Address Not Found" when I try to open local hostname. Using IP:port works, but its been working fine before we moved. Chrome on Android works fine, desktop PC works fine.
Im running pihole and nginx proxy manager on server (I reconfigured pihole, but settings should be the same as before). I have set server IP in router DNS settings. I have set static IP for wifi network on phone and DNS address of server (I think I didnt need this before, but now it doesnt work in chrome without it). I have 2nd pihole on rpi4 as secondary DNS server on both router and phone settings, but its not in use yet. When I reconnect to wifi firefox can open the page for like first 20 sec and then it stopps working.
What am I doing wrong? Ive been using firefox on android exclusively before we moved
Please check https://support.mozilla.org/en-US/kb/canary-domain-use-application-dnsnet
It might be that Firefox on Android is defaulting to only DNS over HTTPS for you
Thx. Is there anything I can do about that?
As per the link you would have to set up the Canary domain. On pihole you can add custom domain names and that should be enough.
Reading the documentation again you should even just be able to blacklist the domain and it'll make Firefox use local DNS in the network.
It took me a while because I replaced 2 routers in meantime. Thanks for tips, but didnt have time to try them. And seems like new router solved the problem somehow. I think it was something with ipv6 that was active while disabled, but just guessing. They replaced 1st router (ZTE) because it had super poor wifi and 2nd one (huawei) because ui was buggy and couldnt change some settings. New huawei seems fine for now and reverse proxy works great.
Thx for help
Check your Android's DNS settings. After that grab a tool like net-tools and see if you can resolve it from there.
After selecting home wifi ssid settings I changed from dhcp to static and set static IP and DNS (my server with pihole + another IP thats not in use yet). In wifi settings under DNS I can see both IP adress that Ive set, but I also see 3rd one that starts like IPV6 address from About Phone section.
Private DNS is off. Is there anything else? Im using Android 12 on Motorola Moto G42 (not rooted).
I got app called Net Tools from play store and I cant ping hostname (Unable to resolve). Pinging local IP works and I can scan opened ports, but cant ping https://192.168.100.40:3300
What can I do? Stupid chrome is working fine...
That's really weird. Is it a normal tld?
Im not sure what you mean. Example is https://jellyfin.tride
Im using self signed certificates if that matters. I used to get certificate warning just like I get in chrome now
That 3rd DNS is weird and also IPV6 that I havent set. IPV6 server is also disabled in router settings
Just to check I’m interpreting this correctly, Chrome on android works, on the same device? (This would verify that all your networking is fine, and that your dns entries are correct for your new network)
Can you see if the firefox local requests are making it to the pihole request log? If they’re not making it there, then we know that it’s got to be an in-app issue.
Could be an issue with dns prefetch caching or something else, narrowing down the scope of checks will focus the troubleshooting more effectively.
Yes, Chrome on Android works. Firefox doesnt trigger anything in pihole query log. I tried to delete data and reinstall firefox, but didnt help. Chrome is making to pihole with no problem. Firefox can sometimes resolve hostname, but for short time only if I just reconnected to wifi.
Will take a look under my bonnet later & get back to you, but as I recall it took a whole lot of trial and error with how I enabled which aspect & in what order. None of which was in any guide, or rather, following what worked for others did not work for me, but am stubborn so got it all working alright in the end (just scared to adjust anything now).