Amahi in its own TLD
Posted: Tue Oct 20, 2009 6:21 am
Currently amahi defaults to home.com for its DNS domain and home for it workgroup domain.
Well there is nothing particularly wrong with home for the workgroup domain, but there is with home.com. First there IS a home.com out there and if any Amahi user needed to access it they could not without major changes to their setup. Then in a SOHO environment, you really can't get systems that are not part of the Amahi domain to access services on the Amahi platform. Even if you were to use foobar.com, you can't set the delegation up for foobar.com pointing to Amahi. I could go on, but then I will be touching on 'RFC purist' issues.
It is easy to set up your own TLD in an internal view. We do this a lot for various testing that needs DNS. I have been running a HTT TLD here for a couple years now.
What I propose is a new direction for DNS for Amahi. I am willing to architect if with full CIDR, both public and private, both IPv4 and IPv6 support. Also delegation to other internal sub-domains or slaving off other internal DNS servers.
I propose 4 choices for DNS domain during install:
<family>.home
<business>.soho
Public registered domain (e.g. home.htt-consult.com for me!)
<user>.amahi.org
Have others thought about this? For the TLD, think about what ICANN will NOT be likely to allocate (and I can always talk to Dave Piscitello there...).
Also need to support multiple Amahi servers per DNS domain. This will be in a separate note.
Well there is nothing particularly wrong with home for the workgroup domain, but there is with home.com. First there IS a home.com out there and if any Amahi user needed to access it they could not without major changes to their setup. Then in a SOHO environment, you really can't get systems that are not part of the Amahi domain to access services on the Amahi platform. Even if you were to use foobar.com, you can't set the delegation up for foobar.com pointing to Amahi. I could go on, but then I will be touching on 'RFC purist' issues.
It is easy to set up your own TLD in an internal view. We do this a lot for various testing that needs DNS. I have been running a HTT TLD here for a couple years now.
What I propose is a new direction for DNS for Amahi. I am willing to architect if with full CIDR, both public and private, both IPv4 and IPv6 support. Also delegation to other internal sub-domains or slaving off other internal DNS servers.
I propose 4 choices for DNS domain during install:
<family>.home
<business>.soho
Public registered domain (e.g. home.htt-consult.com for me!)
<user>.amahi.org
Have others thought about this? For the TLD, think about what ICANN will NOT be likely to allocate (and I can always talk to Dave Piscitello there...).
Also need to support multiple Amahi servers per DNS domain. This will be in a separate note.
