social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

488
active users

#itsalwaysdns

2 posts2 participants1 post today
Continued thread

Hunting the forums turns up at least one person who ran into this on a non-image-based install and determined that the installer is setting resolv.conf to 127.0.0.1 before attempting to download this URL - and apparently before turning up a local resolver. So, yeah, no surprise it can't access the URL.

How this has not been noticed/fixed in 5 months is beyond my comprehension.

ETA: Okay the below is fixed, but why would db.root not update when everything else does?

(it's on Debian)

-----

okay this is weird

the root hints file I have diffs identically to the one I just pulled down from the internic as a sanity check (other than the last updated date which is also weird)

but I'm getting this regardless:

named[1252171]: checkhints: b.root-servers.net/A (170.247.170.2) missing from hints
named[1252171]: checkhints: b.root-servers.net/A (199.9.14.201) extra record in hints

(and similar for the IP6, elided for space)

why

I woke up from a dream where the global internet was down. People running around panicing in their smart houses, not knowing where to get news or music and phonecalls not going through.

I think one of my last thoughts before waking up was "oh well, at least I have a lot of music locally".

The root cause for the global problem was DNS (ofc).

Looks like @mikrotik have got problems... Trying to work out why some of my home kit wasn't accessible and I've just been called by a customer with the same problem. The forum's generating a 500, so no help there...
Turns out their dynamic DNS service is broken. A quick fix to hard code the external IPs in DNS and we're both running again.
#itsalwaysdns #mikrotik #routeros

Continued thread

Actually it looks like one of my VPS IPv6 changed which I used for Monitoring the IPv6 WAN Gateway in #OPNsense..
additionally python used nearly 100% CPU.. which was the Netflow. Don’t know why I had this on.
So I‘m not monitoring the Gateway anymore for now to keep is just running.

CPU is down again to max 30%.

And having DNS on that same host is really bad, because my whole HomeLab including HomeAssistant dies even for reaching local systems.

Away from home at the moment and just remembered I packed my little GL-MT3000 travel router. Fired it up, connected it to the guest WiFi where we are and as planned it "phones home" to connect to a self hosted Wireguard peer, in the process giving my filtered DNS thanks to pihole and tunnels all my traffic through the Wireguard tunnel so it's hidden from prying eyes. I had my phone connecting back home anyway, this just means a little less battery drain and I get to test it properly instead of on my phone hotspot.

So far, so good, except for home server DNS. Wth.... Ahhhh, that's because I started updating all the local DNS records for my home servers but never finished and obviously I picked a server I hadn't updated yet.

Current computer problem that I'm facing (aside from running low of space): large worlds in VRChat will take forever to download. They download normally for ~10 seconds then slow down to a crawl.

VRChat just suggests that I just install *more* software so that ...Cloudflare works better? I don't trust that at all.

EDIT: Changing the DNS from my provider's DNS servers to Cloudflare (on VRC's suggestion) fixed the issue. #itsAlwaysDNS