Talk:Aux root: Difference between revisions
m (Root moved page Talk:Alt root to Talk:Aux root) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
<div style="background-color: antiquewhite;color: navy;"> | <div style="background-color: antiquewhite;color: navy;"> | ||
<blockquote><br><blockquote> | <blockquote><br><blockquote> | ||
This page is a model for the caveat in the README for this domain space as the software underlying it is well worn stuff like BIND9 with just the use, context and supporting function being distinct. | This page is a model for the caveat in the README for this domain space as the software underlying it is well worn stuff like BIND9 with just the use, context and supporting function being distinct and novel. | ||
I have been serving .dom for 4 or 5 years at this writing so it « simply » a matter of providing automation and other support for what now works only | I have been serving .dom for 4 or 5 years at this writing so it « simply » is a matter of providing automation and other support for what now works only by manual intervention. And I might say, somewhat strenuous intervention because in some cases the name service is so aggressively owned that taking control of it and setting desired servers is onerous. Nonetheless, it's within system service norms in that respect and those that can wrest control and set as indicated will see the .dom TLD now. | ||
This is mostly true for resolvconf type servers where multiple agents may act to set a configuration, on end consumer platforms like Windows and Mac it's simpler. [[User:Root|Root]] ([[User talk:Root|talk]]) 14:48, 3 May 2019 (UTC) | |||
</blockquote><br></blockquote> | </blockquote><br></blockquote> | ||
</div> | </div> | ||
Latest revision as of 09:17, 11 May 2022
About this page
This page is a model for the caveat in the README for this domain space as the software underlying it is well worn stuff like BIND9 with just the use, context and supporting function being distinct and novel.
I have been serving .dom for 4 or 5 years at this writing so it « simply » is a matter of providing automation and other support for what now works only by manual intervention. And I might say, somewhat strenuous intervention because in some cases the name service is so aggressively owned that taking control of it and setting desired servers is onerous. Nonetheless, it's within system service norms in that respect and those that can wrest control and set as indicated will see the .dom TLD now.
This is mostly true for resolvconf type servers where multiple agents may act to set a configuration, on end consumer platforms like Windows and Mac it's simpler. Root (talk) 14:48, 3 May 2019 (UTC)
