@[email protected] to [email protected] • 1 year agothanks lain (rule)lemmy.blahaj.zoneimagemessage-square94fedilinkarrow-up1860
arrow-up1860imagethanks lain (rule)lemmy.blahaj.zone@[email protected] to [email protected] • 1 year agomessage-square94fedilink
minus-squareunalivejoylinkfedilinkEnglish17•1 year agoIn my defense, whenever there’s a networking issue, it’s always DNS related.
minus-square@[email protected]linkfedilink44•1 year agoThe three stages of grief: It can’t be DNS There’s no way it could be DNS It was DNS
In my defense, whenever there’s a networking issue, it’s always DNS related.
The three stages of grief:
DNS being down is why the DHCP server didn’t start ;)
I can totally see dnsmasq causing this sort of thing.