• 0 Posts
  • 303 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle



  • I can run app based routing and blocking on my router, but whether that would restrict DNS for those services I don’t know.

    That’s the double-edged sword of DNS over https. It allows us to hide our DNS queries from local ISP and others, but it also allows applications to hide theirs also. It just looks like encrypted web traffic to your router.


  • non_burglar@lemmy.worldtoSelfhosted@lemmy.worldBeyond Pi-Hole
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    5 days ago

    Not sure what you mean by “network based dns”.

    Hard-coded DNS is in the application, you cannot change this from any dhcp option. Browsers do it, lots of versions of prime video apps do it. Google nest and home devices are famous for this.

    You can write a NAT rewrite rule at your router to catch any UDP or TCP request on port 53 and send it to your ad-blocking DNS server/forwarder, but you won’t be able to stop DoH (DNS over https), which just leaves the subnet encrypted on 443.







  • Well, it wouldn’t hurt anything to install fail2ban and enable the popular templates, but it sounds like you might need to explain your service layout and how it’s exposed to the web before anyone can suggest a security measure.

    Generally in the self-hosted space there are two common approaches: set up a VPN into your network for your trusted devices, or set up a reverse-proxy with a trusted tunneling proxy like cloudflare.

    That you are seeing “attack attempts” in your caddy logs should be elaborated as well. What exactly are you seeing?




  • It never worked well for me. Not because it couldn’t fetch ebooks, but because it defaults to adding an author’s entire library, which was dumb for my reading habits.

    I would search for a book, find it, only be able to add the author, and then have to uncheck almost all the books the author had written because I just wanted one.

    Sorting by “books” just showed me a list of hundreds of books when I just wanted 7 of those.

    If your workflow matched that for readarr, I’m sure it worked well, metadata problems aside.







  • No, it is not fully working.

    Many have tried to explain to you that your setup only works for YOU on YOUR subnet.

    Your are then asking other public tools meant to lookup public ips with publicly-available DNS names to resolve your internal addresses, which they obviously don’t know anything about, and you’re getting those errors from tools that follow rfc because you are putting the equivalent of “bedroom” on the outside of an envelope and expecting the post office to know that it means YOUR bedroom.

    For dns to work properly, the authoritative DNS server should be able to create a reverse lookup record for every a record that allow a DNS client to ask “what record do you have for this IP?” and get a coherent response. Since 192.168.10.0/24 is a non-routable network, you will never have such a reverse record.

    Wolfgang has done you a disservice by giving you a shortcut that works as a side-effect of dns before you fully understood how DNS works.