Interstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 2 months agothanks lain (rule)lemmy.blahaj.zoneimagemessage-square86fedilinkarrow-up1851arrow-down10file-text
arrow-up1851arrow-down1imagethanks lain (rule)lemmy.blahaj.zoneInterstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 2 months agomessage-square86fedilinkfile-text
minus-squareunalivejoy@lemm.eelinkfedilinkEnglisharrow-up17·2 months agoIn my defense, whenever there’s a networking issue, it’s always DNS related.
minus-square4am@lemm.eelinkfedilinkarrow-up44·2 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·2 months agoDNS being down is why the DHCP server didn’t start ;)
minus-squaredustycups@aussie.zonelinkfedilinkarrow-up2·2 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.