Interstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 5 months agothanks lain (rule)lemmy.blahaj.zoneimagemessage-square89fedilinkarrow-up1827arrow-down10file-text
arrow-up1827arrow-down1imagethanks lain (rule)lemmy.blahaj.zoneInterstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 5 months agomessage-square89fedilinkfile-text
minus-squareunalivejoy@lemm.eelinkfedilinkEnglisharrow-up17·5 months agoIn my defense, whenever there’s a networking issue, it’s always DNS related.
minus-square4am@lemm.eelinkfedilinkarrow-up41·5 months agoThe three stages of grief: It can’t be DNS There’s no way it could be DNS It was DNS
minus-squareOsaErisXero@kbin.runlinkfedilinkarrow-up4·5 months agoDNS being down is why the DHCP server didn’t start ;)
minus-squaredustycups@aussie.zonelinkfedilinkarrow-up2·5 months agoI can totally see dnsmasq causing this sort of thing.
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.