180

In conclusion: Magic DNS (tesseract.dubvee.org)

submitted 1 week ago by ptz@dubvee.org to c/programmer_humor@programming.dev

14 comments fedilink hide all child comments

top 14 comments

sorted by: hot top controversial new old

[-] Technus@lemmy.zip 38 points 1 week ago

Who tf actually uses Docker Swarm anyway?

[-] derpgon@programming.dev 11 points 1 week ago

For when setting up a kube cluster is too time consuming and you still need basic clustering.

[-] locuester@lemmy.zip 7 points 1 week ago

I do for a small home pi cluster

[-] underscores@lemmy.zip 6 points 1 week ago* (last edited 1 week ago)

We use docker swarm at work. We have 0 issues with it.

[-] in_my_honest_opinion@piefed.social 19 points 1 week ago

Not indexing from 0? Now I see why you're not using quadlets or k3s or k8s

[-] Hexarei@beehaw.org 3 points 1 week ago

K3s powers my homelab! Delightful thing, that

[-] negativenull@piefed.world 12 points 1 week ago

When I try to explain what I'm working on at work to my wife...

[-] funkajunk@lemmy.world 6 points 1 week ago

Kubernetes

[-] WhyJiffie@sh.itjust.works 2 points 1 week ago

what's more, I can't load this meme normally, my pihole says "no reply received" for the single domain of dubvee.org

[-] ptz@dubvee.org 3 points 1 week ago* (last edited 1 week ago)

Your IP may unfortunately be inside a CIDR block that largely does nothing but spam my infrastructure with script kiddie tomfoolery. Firewall rules apply to my authoritative DNS servers as well.

Edit: If you would like me to whitelist it, DM me your IP and I'll add a narrow exception.

[-] WhyJiffie@sh.itjust.works 2 points 1 week ago

but I don't run a recursive resolver, I use quad9 as upstream. Shouldn't they return a response even if I was blocked?

dig confirms with EDNS extensions that the response is coming from quad9. the error says "no reachable authority" so it must be at least partly what you say, but I think you ended up blocking a DNS provider.

[-] ptz@dubvee.org 1 points 6 days ago

FYI: I moved the allow rule for DNS to the top of the chain, so that should fix problems with DNS providers not being able to reach the authoritative name servers.

[-] WhyJiffie@sh.itjust.works 2 points 6 days ago

thanks, it seems it worked! the post image now loads fine

[-] ptz@dubvee.org 3 points 1 week ago* (last edited 1 week ago)

Ugh. Thanks. It's quite possible, though maybe just a regional one? I did inadvertently block one of the IPs Let's Encrypt uses for secondary validation, so this may be another case of that.

I get a shitload of bad traffic from the southeast Asia area (mostly Philippines/Singapore AWS) and have taken to blanket blocking their whole routes rather than constantly playing whack-a-mole. Fail2ban only goes so far for case-by-case.

Here's the image from the meme from an alternate source: