I just run (shall we add the word) “proper” split DNS with the same names for anything publicly exposed, internal. And not everything is publicly exposed. It’s just a standard registered TLD.
It’s interesting how few responses here mention this. Why memorize two or more names for the same box/service when DNS easily handles it?
DHCP clients set their own internal DNS names internally or are forced at the DHCP server. Static addresses via MAC as desired.
They also get handed all the usual SRV records and special record types to find services, like the time server and such.
Truly interesting that split DNS isn’t popular amongst the self hosting crowd.
Type the name of the “thing” after setting it up correctly and you’ll be handed an appropriate address to reach it, no matter which of my networks you’re on.
If you’re a dhcp client you’ll have the proper search domain handed right to you too, no need to even type the domain.tld at all. Just the hostname.
I just run (shall we add the word) “proper” split DNS with the same names for anything publicly exposed, internal. And not everything is publicly exposed. It’s just a standard registered TLD.
It’s interesting how few responses here mention this. Why memorize two or more names for the same box/service when DNS easily handles it?
DHCP clients set their own internal DNS names internally or are forced at the DHCP server. Static addresses via MAC as desired.
They also get handed all the usual SRV records and special record types to find services, like the time server and such.
Truly interesting that split DNS isn’t popular amongst the self hosting crowd.
Type the name of the “thing” after setting it up correctly and you’ll be handed an appropriate address to reach it, no matter which of my networks you’re on.
If you’re a dhcp client you’ll have the proper search domain handed right to you too, no need to even type the domain.tld at all. Just the hostname.