Interstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 15 days agothanks lain (rule)lemmy.blahaj.zoneimagemessage-square95fedilinkarrow-up1853arrow-down11file-text
arrow-up1852arrow-down1imagethanks lain (rule)lemmy.blahaj.zoneInterstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 15 days agomessage-square95fedilinkfile-text
minus-squareunalivejoylinkfedilinkEnglisharrow-up17·15 days agoIn my defense, whenever there’s a networking issue, it’s always DNS related.
minus-square4amlinkfedilinkarrow-up44·15 days 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·15 days agoDNS being down is why the DHCP server didn’t start ;)
minus-squaredustycups@aussie.zonelinkfedilinkarrow-up2·15 days 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.