• 1 Post
  • 11 Comments
Joined 7 months ago
cake
Cake day: January 28th, 2025

help-circle
  • More like unpopular opinion.

    But I mostly agree, always better also for your health to cook at home.

    But everyone deserves a threat and if you live in the USA, then tip is required…

    Stupid and idiot thing, i am grateful I don’t live there for this reason. I spent time and lived in the USA 20 years ago… I never complained for tipping, nut now I am only baffled at wht it has become today your tipping culture.








  • Shimitar@downonthestreet.eutoSelfhosted@lemmy.worldDNS server
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    15 days ago

    Above some threshold, the one you will cross when filtering port 53 in your network and setup a custom full resolver, it can happen.

    I experienced it, it seems they filter excess dns traffic from inside. Probably more a malware/anti spam measure than an actually DNS blocking.


  • Shimitar@downonthestreet.eutoSelfhosted@lemmy.worldDNS server
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    3
    ·
    edit-2
    15 days ago

    My 2c.

    Changing “DNS” won’t fix it. There are two DNS: dnsmasq and unbound (and bind, ok). What else you use doesn’t matter (pihole, adguard, opnSense) at the end of the day it’s always them inside.

    In my experience ISPs will block your direct DNS queries overtime, so it might be that. I set up my unbound as caching and forwarding, not as a pure resolver. This fixed all my issues with DNS self hosted. You can forward to 9.9.9.9 if you like it.

    Another issue might be with your blocklists of course, your azure might have been temporary listed maybe.

    Over time I ended up choosing a very lax blocklist setup due to this reason