Interstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 12 days agothanks lain (rule)lemmy.blahaj.zoneimagemessage-square86fedilinkarrow-up1848arrow-down10file-text
arrow-up1848arrow-down1imagethanks lain (rule)lemmy.blahaj.zoneInterstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 12 days agomessage-square86fedilinkfile-text
minus-squareunalivejoy@lemm.eelinkfedilinkEnglisharrow-up10·edit-212 days agoThat just means the DNSDHCP is disabled. Edit: words
minus-squarecerement@slrpnk.netlinkfedilinkarrow-up23·12 days ago “The hotel’s free WiFi is really fast” “the DNS is disabled”
minus-squareOsaErisXero@kbin.runlinkfedilinkarrow-up23·12 days agoThat is not what that means, it means there’s no dhcp on that network segment.
minus-squareunalivejoy@lemm.eelinkfedilinkEnglisharrow-up17·12 days agoIn my defense, whenever there’s a networking issue, it’s always DNS related.
minus-square4am@lemm.eelinkfedilinkarrow-up44·12 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·12 days agoDNS being down is why the DHCP server didn’t start ;)
minus-squaredustycups@aussie.zonelinkfedilinkarrow-up2·12 days agoI can totally see dnsmasq causing this sort of thing.
That just means the
DNSDHCP is disabled.Edit: words
That is not what that means, it means there’s no dhcp on that network segment.
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.