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!

  • volle@feddit.de
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    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.

  • filister@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Try with dig to check what DNS you are using. And check if you have support for both IPv4 and IPv6.

    • iturnedintoanewt@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      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?

  • flathead@quex.cc
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    is your router’s dns definitely pointed to the pihole and was the router rebooted after that was set?

  • iturnedintoanewt@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      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.