Hi, I’m hosting an own dns-server in my home-network, so that I can access my server in my private network with a domain without buying that domain. It works fine on my computer, but when I’m typing in the domain of my server on my smartphone, the browser doesn’t resolve to the local ip of my webserver.

I already tried to change the dns-entry in the settings manually, but it doesn’t worked. Do anybody of you faced the same problem or has a good solution for my problem?

  • ExoWire@alien.topBEnglish
    2·
    1 year ago

    I had a similar problem. Solution was to deactivate IPv6 support in the routing device.

  • thekrautboy@alien.topBEnglish
    1·
    1 year ago

    but it doesn’t worked

    So many details.

    Why not use some type of “network info tool” app to find out which DNS servers are actually being used and what their replies are?

    Android is well known of often sneaking in the Google DNS servers (8.8.8.8 and 8.8.4.4 for IPv4) if you only enter one DNS server in the network options of your WLAN. Place your own DNS into both fields. Some Android ROMs complain then that they are identical, in that case try to enter 127.0.0.1 or 0.0.0.0 for example as one, if that also doesnt work then just make up another IP that fits your network. It will send requests into nowhere but since the other one is working, it doesnt matter much.

    A lot of Android ROMs also have “Private DNS” enabled by default. Disable that, it might be the reason its bypassing your local DNS (Pihole, Adguard Home, whatever).

    And some users mistakenly enter their own local DNS (like a Pihole) into the “Private DNS” option.

    What is also possible is that some apps have their own builtin “by-pass”, for example they might use DNS-over-TLS or DNS-over-HTTPS (DoT/DoH) to make encrypted DNS requests to fixed servers, completely ignoring whatever you set in the OS network config.

    /r/Android and /r/HomeNetworking can help.

    • ButCaptainThatsMYRum@alien.topBEnglish
      1·
      1 year ago

      Commented with my fix; in pfSense I have all port 53 traffic redirected with a NAT rule. Works great and catches any devices with hardcoded DNS.

  • lilolalu@alien.topBEnglish
    1·
    1 year ago

    I have the same issue with my xiaomi 12x, before with a OnePlus 5t, but I gave up on it. It’s not a Google Pixel issue but in my observation a Google Chrome Issue. Firefox on the phone uses the DNS that DHCP defined for the devices, chrome ignores them and uses googles DNS. I don’t know if that’s “on purpose” or a bug, I find it pretty annoying - but what can you do…

    Whenever I need to access a locally defined URI, like “netdata.home” I open it on Firefox.