home.social

#blocky — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #blocky, aggregated by home.social.

fetched live
  1. @freezr You can also setup an ads and trackers block using #PiHole or #AdGuardHome or #Blocky with the good blocklists.

  2. Learned about #splitdns today. i have experimented with #blocky dns server which worked fine now i want to try out with split dns I guess it won't cut out for this so alternative would be #AdGuardHome which is written in #go and the release are single binary (easy to test) with web ui.

    TLDR: Split DNS, or split-horizon DNS, is a networking technique providing different DNS results for the same domain name based on the user's location (internal vs. external)

  3. Learned about #splitdns today. i have experimented with #blocky dns server which worked fine now i want to try out with split dns I guess it won't cut out for this so alternative would be #AdGuardHome which is written in #go and the release are single binary (easy to test) with web ui.

    TLDR: Split DNS, or split-horizon DNS, is a networking technique providing different DNS results for the same domain name based on the user's location (internal vs. external)

  4. @blindcoder Just looked up the #DNS ad blocking landscape last night.

    Seems like #PiHole is slowly coming out of fashion and more seen as the "simple beginner's tool". #AdGuard is what most people seem to use nowadays. (That's also what's integrated into #GLiNet routers!) And the real geeks apparently use #Technitium (.NET!).

    Some pay for #NextDNS.io as they don't want to host "such essential service" themselves. Also, you can use it from everywhere without the need for VPN tunnels or open ports into your home for DoH/DoT.

    And #Blocky got honorary mentions from some masochists.

  5. @blindcoder Just looked up the #DNS ad blocking landscape last night.

    Seems like #PiHole is slowly coming out of fashion and more seen as the "simple beginner's tool". #AdGuard is what most people seem to use nowadays. (That's also what's integrated into #GLiNet routers!) And the real geeks apparently use #Technitium (.NET!).

    Some pay for #NextDNS.io as they don't want to host "such essential service" themselves. Also, you can use it from everywhere without the need for VPN tunnels or open ports into your home for DoH/DoT.

    And #Blocky got honorary mentions from some masochists.

  6. I've essentially wasted the entire day messing around with #Blocky, setting up #Telegraf and building a dashboard from the Blocky data. I definitely did NOT need to be working on that... :nkoCrying: :nkoFacePalm:

    #data #visualization #Grafana #Prometheus #InfluxDB #ADHD

  7. I've essentially wasted the entire day messing around with #Blocky, setting up #Telegraf and building a dashboard from the Blocky data. I definitely did NOT need to be working on that... :nkoCrying: :nkoFacePalm:

    #data #visualization #Grafana #Prometheus #InfluxDB #ADHD

  8. #Linux #Dns #Blocky
    Y'a des utilisateurs de Blocky, ici ?
    J'ai un soucis.
    Je l'ai configuré en DNS "normal", DoT et DoH.
    J'ai configuré Firefox pour pointer sur le DoH. Dans les logs de Blocky le vois bien arriver les requêtes de Firefox et il y répond bien (response_type=RESOLVED) mais ne semble jamais utiliser le cache (jamais response_type=CACHED).

    Quand je fais des "dig" sur le port non chiffré, je vois bien des mises en cache.

    Une idée ?

  9. #Linux #Dns #Blocky
    Y'a des utilisateurs de Blocky, ici ?
    J'ai un soucis.
    Je l'ai configuré en DNS "normal", DoT et DoH.
    J'ai configuré Firefox pour pointer sur le DoH. Dans les logs de Blocky le vois bien arriver les requêtes de Firefox et il y répond bien (response_type=RESOLVED) mais ne semble jamais utiliser le cache (jamais response_type=CACHED).

    Quand je fais des "dig" sur le port non chiffré, je vois bien des mises en cache.

    Une idée ?

  10. I moved all my servers at home over to their own profile in #NextDNS. They no longer go through my local #Blocky instance. Other devices (desktops, laptops, mobile devices, etc...) seem to be loading services much quicker now.

  11. I moved all my servers at home over to their own profile in #NextDNS. They no longer go through my local #Blocky instance. Other devices (desktops, laptops, mobile devices, etc...) seem to be loading services much quicker now.

  12. In den letzten Tagen wurde eine Blockliste geteilt, dass die Webseiten vom Axel Springer Konzern geblockt werden.

    Habe die endlich mal zu meinem Werbeblocker #blocky hinzugefügt. Dazu auch mal einen Blogbeitrag (teqqy.de/3-dns-blocklisten-fue ) damit aktualisiert.

    github.com/autinerd/anti-axels

  13. Today I found #Blocky. A cool #PiHole alternative that is available in the nix packages. I configure Blocky, integrate it into Grafana and find that I can't edit the DHCP Server in my plastic router. Now I'm sitting here and looking at how I can build my own #NixOS router. Typical course of projects. -.-

  14. Today I found #Blocky. A cool #PiHole alternative that is available in the nix packages. I configure Blocky, integrate it into Grafana and find that I can't edit the DHCP Server in my plastic router. Now I'm sitting here and looking at how I can build my own #NixOS router. Typical course of projects. -.-

  15. Note to self: When converting a Kubernetes cluster with Cilium as CNI to replace MetalLB with Cilium's new L2 announcements, you need to tweak some settings in your Cilium installation. Especially enabling Cilium to act as a kube-proxy replacement (if you are not already doing so) and enabling the l2 announcements. Which means kube-proxy needs to be disabled in k3s.

    In other words: k3s on my Raspi4 is now providing a loadbalancer to blocky using Cilium's L2 announcements...

    #kubernetes #k3s #cilium #homelab #metalLB #loadbalancer #dns #blocky #hellyeah

  16. Note to self: When converting a Kubernetes cluster with Cilium as CNI to replace MetalLB with Cilium's new L2 announcements, you need to tweak some settings in your Cilium installation. Especially enabling Cilium to act as a kube-proxy replacement (if you are not already doing so) and enabling the l2 announcements. Which means kube-proxy needs to be disabled in k3s.

    In other words: k3s on my Raspi4 is now providing a loadbalancer to blocky using Cilium's L2 announcements...

    #kubernetes #k3s #cilium #homelab #metalLB #loadbalancer #dns #blocky #hellyeah

  17. New kid on the #Blocky: Adblocker für das Heimnetz. Hat das jemand statt Pihole oder Adguard im Einsatz und kann kurz von Erfahrungen berichten? 0xerr0r.github.io/blocky/main/

  18. I couldn't leave well enough alone in the #homelab I put #dnsdist back in the mix balancing 2 #coredns servers for my services based on source and then the rest going to #blocky. I gotta set vrrp with one more instance of dns dist and I got so much overkill of DNS for no for fucking reason!

  19. I'm not exactly sure how I got here! I been trying to figure out my DNS infra for some damn reason. It's DNS who the fuck cares. I can't let it go!

    I just want to exercise my second DNS server, cause it's just there. So lets put #dnsdist in front of it, solid!. It gave me a promfana endpoint to see shit. Dope! Then I'm like I want that for my DNS servers! Insert #coredns. It's coo! Fast! Easy to use! Ad blocking, not so much. Insert #blocky. Ok WTF is going on!

    #homelab #selfhosted