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?
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 :(
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.
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@127@lemmy.world which server is configured in your machine (/etc/resolv.conf in linux, or in system preference in Mac). My first guess would be to check what is your computer using as a DNS ip
@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 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
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
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 :(
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.
is your router’s dns definitely pointed to the pihole and was the router rebooted after that was set?
If you mean by the DNS provided by the router on DHCP, yes, they are.
Try with dig to check what DNS you are using. And check if you have support for both IPv4 and IPv6.
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?
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.
Rate limited…by whom? I’m using unbound, so I’m not forwarding my DNS requests to my ISP.
By pihole. Iirc the default limit is 1000 requests per minute
@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 ipI use linux, yeah. nameserver is 127.0.0.53 (?). search is pointing to the pihole server.
@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 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
Sorry…what do you mean changing the resolv to the up of the pihole? I’m a bit lost here 😅