July 27, 20232 yr tower-diagnostics-20230727-2302.zipfile:///C:/Users/Mike/Downloads/tower-diagnostics-20230727-2302.zip It stopped working out of nowhere. I tried stopping all my docker apps, but still no internet. I have no clue what to do to fix this, hopefully someone can help Edited July 27, 20232 yr by Deagarys
July 27, 20232 yr Author For some reason i cannot ping google .com but i can ping 142.250.179.206 which is google their ip Edited July 27, 20232 yr by Deagarys
July 27, 20232 yr Author 5 minutes ago, Vr2Io said: Check DNS setting. Where? I am completely new to this. This is my second day of having the tower This is what i can find: Edited July 27, 20232 yr by Deagarys
July 27, 20232 yr In network page. I haven't check the diagnostics due to browsing with mobile. You setting in auto IP ( dhcp ) or manual IP ( static ）?
July 27, 20232 yr Author 1 minute ago, Vr2Io said: In network page. I haven't check the diagnostics due to browsing with mobile. You setting in auto IP ( dhcp ) or manual IP ( static ）? I just edited my previous reply with a screenshot of my network settings.
July 27, 20232 yr You sure you have local dns on 192.168.1.1 ? Usually the dns are same as gateway, so check your router DHCP dns setting. Edited July 27, 20232 yr by Vr2Io
July 27, 20232 yr Author 192.168.1.1 is my pi hole which is the dns of my router. This has been working for 12hrs now or something like that and suddenly just stopped working. only on my server everything else has internet. Edited July 27, 20232 yr by Deagarys
July 27, 20232 yr Then check at pihole FTL log and check does receive and reply Unraid's request. Or simple try use router for dns resolve, if problem solve, it is pihole issue.
July 27, 20232 yr Author I changed my routers DNS back to it's own. Restarted it all the internet came back, but not on my server yet. Issue is not with pi hole i suppose.
July 27, 20232 yr Community Expert Change your DNS from 192.168.1.1 to cloudfare, Google, 9s... See if you still have the problem. If the problem goes away, it is your dns setting within 192.168.1.1. if problem persists, there is another network issue at hand. Dns servers: 1.1.1.1 8.8.8.8 9.9.9.9 208.67.222.222
July 28, 20232 yr Author Solution SOLUTION: The issue was that the DNS on my Tower was pointed towards my Pi-Hole. I turned automatic DNS off and back on. This seemed the fix the issue. I now took the automatic DNS and made that ip my static DNS so it will not target Pi-Hole automatically again.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.