Interstellar_1 ( Interstellar_1@lemmy.blahaj.zone ) to 196@lemmy.blahaj.zone · 2 years agothanks lain (rule)lemmy.blahaj.zoneimagemessage-square48linkfedilinkarrow-up1482file-text
arrow-up1482imagethanks lain (rule)lemmy.blahaj.zoneInterstellar_1 ( Interstellar_1@lemmy.blahaj.zone ) to 196@lemmy.blahaj.zone · 2 years agomessage-square48linkfedilinkfile-text
minus-squareunalivejoy ( joyjoy@lemm.ee ) linkfedilinkEnglisharrow-up14·2 years agoIn my defense, whenever there’s a networking issue, it’s always DNS related.
minus-square4am ( 4am@lemm.ee ) linkfedilinkarrow-up31·2 years agoThe three stages of grief: It can’t be DNS There’s no way it could be DNS It was DNS
minus-squareOsaErisXero ( OsaErisXero@kbin.run ) linkfedilinkarrow-up3·2 years agoDNS being down is why the DHCP server didn’t start ;)
minus-squaredustycups ( prex@aussie.zone ) linkfedilinkarrow-up2·2 years 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.