Eager Eagle@lemmy.world to Selfhosted@lemmy.worldEnglish · 9 months agoICANN proposes creating .INTERNAL domainwww.theregister.comexternal-linkmessage-square52fedilinkarrow-up1171arrow-down14 cross-posted to: sysadmin@lemmy.world
arrow-up1167arrow-down1external-linkICANN proposes creating .INTERNAL domainwww.theregister.comEager Eagle@lemmy.world to Selfhosted@lemmy.worldEnglish · 9 months agomessage-square52fedilink cross-posted to: sysadmin@lemmy.world
minus-squaresir_reginald@lemmy.worldlinkfedilinkEnglisharrow-up1·9 months agoI think needing a VPN to access the internal network is a good practice. And if you’re going to be used a VPN anyway, I don’t see why you wouldn’t use a “fake” TLD like .lan for internal stuff, after all it’s just simple DNS rules.
minus-squarefishpen0@lemmy.worldlinkfedilinkEnglisharrow-up1·9 months agoVPN is inherently not zero trust. You really should be moving to ZTN based tools
I think needing a VPN to access the internal network is a good practice. And if you’re going to be used a VPN anyway, I don’t see why you wouldn’t use a “fake” TLD like .lan for internal stuff, after all it’s just simple DNS rules.
VPN is inherently not zero trust. You really should be moving to ZTN based tools