thanks lain (rule)lemmy.blahaj.zoneimage Interstellar_1 ( @Interstellar_1@lemmy.blahaj.zone ) 196@lemmy.blahaj.zone • 3 months ago message-square48fedilinkarrow-up1481
arrow-up1481imagethanks lain (rule)lemmy.blahaj.zone Interstellar_1 ( @Interstellar_1@lemmy.blahaj.zone ) 196@lemmy.blahaj.zone • 3 months ago message-square48fedilink
minus-square unalivejoy ( @joyjoy@lemm.ee ) linkfedilinkEnglish14•3 months agoIn my defense, whenever there’s a networking issue, it’s always DNS related.
minus-square 4am ( @4am@lemm.ee ) linkfedilink31•3 months agoThe three stages of grief: It can’t be DNS There’s no way it could be DNS It was DNS
minus-square OsaErisXero ( @OsaErisXero@kbin.run ) linkfedilink3•3 months agoDNS being down is why the DHCP server didn’t start ;)
minus-square dustycups ( @prex@aussie.zone ) linkfedilink2•3 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.