[deleted]

Comments

• redlemace@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  They always point at the network, but we know: Image

  source
• MangoPenguin@lemmy.blahaj.zone ⁨3⁩ ⁨weeks⁩ ago

  I’m not sure what you’re doing with a public CNAME pointing to a local alias?

  A local service lookup like from your screenshot should be happening directly on the local DNS server, it shouldn’t be going out to any upstream DNS server…

  source

  • qaz@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Since the records have TTL of 5 minutes wouldn’t dnsmasq have to reach to upstream DNS servers every 5 minutes?

    source

    • MangoPenguin@lemmy.blahaj.zone ⁨3⁩ ⁨weeks⁩ ago

      Only for records on the public internet. Local DNS records are done locally. Unless you’re not using local DNS records or something?

      source
• glizzyguzzler@lemmy.blahaj.zone ⁨3⁩ ⁨weeks⁩ ago

  I have my router (opnsense) redirect all DNS requests to pihole/adguardhome. AdGuard home is easier for this since you can have it redirect wildcard *.local.domain while pihole wants every single one individually (uptime.local.domain, dockage.local.domain). With that combo of router not letting DNS out to upstream servers and my local DNS servers set up to redirect *.local.domain to the correct location(s), my DNS requests inside my local network never get out where an upstream DNS can tell you to kick rocks.

  I combined the above with a (hella cheap for 10yr) paid domain, wildcard certified the domain without exposure to the wan (no ip recorded, but accepted by devices), and have all *.local.domain requests redirect to a single server caddy instance that does the final redirecting to specific services.

  I’m not fully sure what you’ve got cooking but I hope typing out what works for me can help you figure it out on your end! Basically the router doesn’t let anything DNS get by to be fucked with by the ISP.

  source

  • qaz@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Thanks for the advice. I also use a cheap domain with a wildcard, but use nginx instead. I just tried using Adguard and although it’s fascinating to see the insights of all the DNS requests, it didn’t really help fix the issue. However, since using DoH with Cloudflare in combination with setting it to the specific IP instead of my local device name and have 100% uptime now (since the last 10 minutes that is).

    source
• AtariDump@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  www.isitdns.com

  source
• catloaf@lemm.ee ⁨3⁩ ⁨weeks⁩ ago

  Have you tried tracing the issue? What is uptimekuma using for DNS? What do the logs on that server show?

  source

  • qaz@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Uptime Kuma seems to use nscd for caching internally and the default system DNS resolver. I’ve added a custom DNS resolvers to Uptime Kuma, and apparently it can get the records from Cloudflare (1.1.1.1) but it can’t get it from the OpenWRT router (192.168.1.1). 🤔

    source