2 ms·

Those specific additional domains are useful in their own ways. .net is good for network infrastructure, .org is good for organizational purposes like mapping y

Those specific additional domains are useful in their own ways. .net is good for network infrastructure, .org is good for organizational purposes like mapping your office/LAN endpoints into it, so that employees could connect to VPNs and internal services like SCM and build servers. Other than that, additional domains also give leverage for diversification if you decide to make them publicly visitable one day.

jcparkyn 3y ago
> .net is good for network infrastructure, .org is good for organizational purposes Genuine question: Is there any tangible/technical benefit to this, or is it just for the sake of keeping them organised?
- brirec 3y ago
  If you deploy a Windows Server AD domain (do people still deploy new AD domains?) it makes things a lot easier and simpler to be able to make it the authoritative DNS servers for a real domain name, and by default it will stomp all over the A/AAAA records for the top of that DNS zone. I can’t really think of anything else that would really benefit from having its own domain though, especially if your DNS infrastructure supports nested zones.
- garganzol 3y ago
  There is a benefit: you do not want to stress your .com domain too much when you provide some network services like discovery services, tunnels etc to your customers. The reason is pragmatic: if a company provides such kind of services then it may fall under a (false) scrutiny one day after somebody uses one of its services for, say, planting a stealth DDoS attack. The whole domain may be yanked or denylisted, and the last domain you want to see under the fire is your .com domain. The same goes to .org: you do not want to see outsiders messing with your organizational endpoints and internal operations, so you better move them to a separate domain for the sake of a) clarity and b) risk hedging. There are two drawbacks though: 1) higher domain costs 2) if you are not careful enough in managing expectations, people may be confused about which one to use and when.
tomas789 3y ago
I'd suggest to not use this technique as it gets quite confusing for others. You have to connect to something and you don't know whether it is .com, .org or what else. It is common to use different dummy names like githubusercontent.com and so. You can easily grab a random name like this and is way less confusing.

jcparkyn 3y ago

> .net is good for network infrastructure, .org is good for organizational purposes Genuine question: Is there any tangible/technical benefit to this, or is it just for the sake of keeping them organised?

brirec 3y ago
If you deploy a Windows Server AD domain (do people still deploy new AD domains?) it makes things a lot easier and simpler to be able to make it the authoritative DNS servers for a real domain name, and by default it will stomp all over the A/AAAA records for the top of that DNS zone. I can’t really think of anything else that would really benefit from having its own domain though, especially if your DNS infrastructure supports nested zones.
garganzol 3y ago
There is a benefit: you do not want to stress your .com domain too much when you provide some network services like discovery services, tunnels etc to your customers. The reason is pragmatic: if a company provides such kind of services then it may fall under a (false) scrutiny one day after somebody uses one of its services for, say, planting a stealth DDoS attack. The whole domain may be yanked or denylisted, and the last domain you want to see under the fire is your .com domain. The same goes to .org: you do not want to see outsiders messing with your organizational endpoints and internal operations, so you better move them to a separate domain for the sake of a) clarity and b) risk hedging. There are two drawbacks though: 1) higher domain costs 2) if you are not careful enough in managing expectations, people may be confused about which one to use and when.

tomas789 3y ago

I'd suggest to not use this technique as it gets quite confusing for others. You have to connect to something and you don't know whether it is .com, .org or what else. It is common to use different dummy names like githubusercontent.com and so. You can easily grab a random name like this and is way less confusing.