Hi guys!
So, it seems I'm getting again stuck with my pihole, seems it might not resolve domains I know that are new to it... So, if I try to visit the website from my browser (firefox or ungoogle chromium), it gets a DNS failure. Same with a nslookup. But if I connect to the pihole and do a: dig saigoneer.com @127.0.0.1 -p 5335 I get the full response and resolution. But even in the pihole, attempting nslookup saigoneer.com will fail. Any idea what can I try next?
Thanks!
15 Comments
volle@feddit.de · 3 pts · 3y
Have you checked if you're rate limited? I was getting rate limited while downloading games from steam which took me several hours to debug.
Not sure if this is your problem but it might be a thing to check out.
iturnedintoanewt@lemmy.world · 1 pts · 3y
Rate limited...by whom? I'm using unbound, so I'm not forwarding my DNS requests to my ISP.
volle@feddit.de · 1 pts · 3y
By pihole. Iirc the default limit is 1000 requests per minute
alvaro@social.graves.cl · 2 pts · 3y
@iturnedintoanewt@lemmy.world @127@lemmy.world which server is configured in your machine (
/etc/resolv.confin linux, or in system preference in Mac). My first guess would be to check what is your computer using as a DNS ipiturnedintoanewt@lemmy.world · 1 pts · 3y
I use linux, yeah. nameserver is 127.0.0.53 (?). search is pointing to the pihole server.
alvaro@social.graves.cl · 2 pts · 3y
@iturnedintoanewt@lemmy.world Ubuntu? What happens if you manually change resolv to the up of your pinhole? I remember Ubuntu has this silly resolvconfd that makes everything more confusing
iturnedintoanewt@lemmy.world · 1 pts · 3y
Sorry...what do you mean changing the resolv to the up of the pihole? I'm a bit lost here 😅
alvaro@social.graves.cl · 1 pts · 3y
@iturnedintoanewt@lemmy.world So what I suspect happens is that you have your pihole server running, but your computer is not using it and instead is querying 1.1.1.1 or other default DNS server.
So what I was thinking is that if that is the case, you can force your computer to use your pihole by editing
/etc/resolv.confto have your pihole's IP as a nameserver.alvaro@social.graves.cl · 2 pts · 3y
@iturnedintoanewt@lemmy.world Ubuntu? What happens if you manually change resolv to the up of your pinhole? I remember Ubuntu has this silly resolvconfd that makes everything more confusing
flathead@quex.cc · 2 pts · 3y
is your router's dns definitely pointed to the pihole and was the router rebooted after that was set?
iturnedintoanewt@lemmy.world · 1 pts · 3y
If you mean by the DNS provided by the router on DHCP, yes, they are.
filister@lemmy.world · 1 pts · 3y
Try with dig to check what DNS you are using. And check if you have support for both IPv4 and IPv6.
iturnedintoanewt@lemmy.world · 2 pts · 3y
I have purposely disabled IPv6 everywhere. Router, Pihole etc. What do you mean which DNS am I using? The computer failing to resolve, or the Pihole that successfully resolves with dig, but somehow fails to actually resolve it to the pihole request/requesting computer?
iturnedintoanewt@lemmy.world · 1 pts · 3y
Welp...Not sure what was wrong, but seems to now be resolving again. I...restored a few previous backups to no avail, rebooted to no avail...and after just giving up and upgrading, and rebooting...now it seems to work again. And I still have no idea how to troubleshoot this if it ever happens again :(
Tunawithshoes@lemmy.blahaj.zone · 3 pts · 3y
This is the reason I stopped unbound. My unbound worked great for years. Suddenly I got this weird issue that was no one could understand why. And after a week of trying to trouble it just decided to work and kept going happily.