A DNS Proxy/Forwarder server? That’s where you would configure how your .internal domain resolves to IPs on your internal network. Machines inside the network make their DNS queries to that server, which either serves them from cache, or from the local mappings, for forwards them off to a public/ISP server.
Comment on ICANN proposes creating .INTERNAL domain
deadcatbounce@reddthat.com 9 months ago
Don’t follow. Help me out someone please.
The net runs on numbers. The numbers have to be translated into/from the DNS name to the numbers.
Nominating a DNS name as internal is doesn’t change the fact that we still have to, at some stage, find the (local) network mask that that it corresponds to.
What am I missing?
JakenVeina@lemm.ee 9 months ago
VelociCatTurd@lemmy.world 9 months ago
It’s for internal resources. You can really use whatever subdomain you want internally, but this decision would be to basically say to registrars, this TLD is reserved, we will never sell this TLD to anyone to use. That way you know that if you use it internally, there’s no way a whoopsie would happen where your DNS server finds a public record for this TLD.
BCsven@lemmy.ca 9 months ago
I assumed that was what .local was all about
VelociCatTurd@lemmy.world 9 months ago
.local is for mDNS addresses.
BCsven@lemmy.ca 9 months ago
Can you explaim further: I’m savvy enough to install a custom kernel for a 14 year old arm board and flush drive boot sector with U boot, etc, so I can use it as a dedicated DAAP server, but Networking somehow eludes me