Yello people.

I found a interesting problem i have trouble fixing after upgrading my network.

it seems my DNS settings are "stuck".

i am capable of manually setting my ip (wich is needed) but i am unable to change my DNS after a network change. i used to be 192.168.1.20 and its been changed to 192.168.1.250.

but unraid refuses to adopt these new 192.168.1.250 setting and remain stuck on 100.100.100.100 for whatever reason. its an adress i never used.

while i am running the latest version i dont expect this issueto be related.

before doing rash stuff i rather hear what the brain trust here has to recommend before breaking stuff.

nasi-diagnostics-20260507-1818.zip

Edited May 7May 7 by thedutchguy

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

8 minutes ago, itimpi said:

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

apologies, i uploaded the wrong file. now fixed.

1 hour ago, thedutchguy said:

and its been changed to 192.168.1.250

According to the diags that is the current DNS

DNS_SERVER1="192.168.1.250"

23 minutes ago, JorgeB said:

According to the diags that is the current DNS

DNS_SERVER1="192.168.1.250"

the info box doesnt say that (its still stuck on 100.100.100.100 and unraid is complaining it cant get online.

note: the dns adress is a pihole and the router enforces all dns traffic to to go the pihole so no devices can bypass adblock and tracking. the pihole does not block any unraid traffic, it just doesnt get any according to its logs.

the home assistant VM and dockers have no problem getting online as they have their ip and dns set in their own settings.

Edited May 7May 7 by thedutchguy

Reboot and retest, if the same, delete/rename /config/network.cfg on the flash drive to go back to default DHCP, then reconfigure.

i did a reboot and unraid can go online now (checking for docker updates and stuff also works normally) so it seems the dns "took" but it still shows 100.100.100.100 on the info popup and verifying with nslookup in the terminal.

after some slight googleing i found that this dns adress is used by tailscale internally. so i expect it actually didnt take and its still stuck on the tailscale dns.

wich begs the question how or why unraid is locked into using my tailscale network as its only "way out" and refuses to accept anything else.

Edited May 10May 10 by thedutchguy

I have Tailscale installed, and it doesn't show as the DNS server, so something else may be going on.

47 minutes ago, JorgeB said:

I have Tailscale installed, and it doesn't show as the DNS server, so something else may be going on.

i agree, the question is what.

i would very much not nuke my install and start over if this is an actual bug of some sorts that i found that can be solved without starting over.

Edited May 10May 10 by thedutchguy

I would start by removing the Tailscale plugin (it won't delete the settings) and retest.