Umbrel keeps overwriting DNS values with 1.1.1.1 and 8.8.8.8

Support and Troubleshooting
1

This is a problem, because in the country my server is in, these DNS servers are blocked :frowning:. I’ve tried various methods, including adding supersede domain-name-servers [address of router]; to the dhcp.conf and restarting, but something continues to overwrite the resolv.conf with Cloudflare and Google DNSs. Note that the above change to dhcp.conf shouldn’t be required, since the DHCP server is providing the correct values.

Any idea what’s causing this and how to stop it? Thanks!

2 Likes
2

I think this may have started with the attempt to update to 0.5.1, as per Umbrel 0.5.1 is out with app release notes and bug fixes

I’ve tried using iptables to remap 1.1.1.1 and 8.8.8.8 to my router/dns proxy, which works for dns lookups on the command line, but most of the apps are still stuck on “starting”.

1 Like
3

Just found these:

./scripts/update/00-run.sh:echo "nameserver 8.8.8.8" >> "${RESOLV_CONF_FILE}"
./scripts/start:DEVICE_IP="$(ip -o route get to 8.8.8.8 | sed -n 's/.*src \([0-9.]\+\).*/\1/p')"
2 Likes
4

Its hardcoded right and they arent addressing the issue. The issue being that it is hardcoded.

2 Likes
5

Added my 2 local pihole dns IP addresses in resolv.conf which allowed me to run the update. Unfortunately resolv.conf gets re-written with Google DNS at reboot.

If this isn’t fixed then Umbrel isn’t for me unfortunately. :frowning:

6

100% ghey.

I am using my own DNS on prem which does DoT to upstream resolvers, umbrel keeps changing /etc/resolv.conf to 1.1.1.1 and 1.0.0.1 which all ordinary DNS over 53 are blocked in my firewall causes umbrel to fail spectaularly.

this trash is going in the bin. Umbrel is not for people who like security and privacy clearly, I’m not willing to regress to old non encrypted DNS just for Umbrel.

7

Hey @river, I was just checking though and I found a GitHub issue referencing the inability to change DNS servers. It looks like Mayank said it was supposed to happen in v1.0.5 but it never was pushed. I think they are now planning it for v1.3.0. However the way this is likely to happen is respecting your router’s DHCP rules for your DNS router. I think they were talking about maybe a bootstrap DNS server for user’s with weird DNS configurations, but probably a toggle in the settings menu.

Since were just working with Debian here, you can configure resolve.conf overwriting on startup, but it’s probably going to break with future updates.

1 Like