[dns-operations] Dumb question: why is it that some registries limit the nameservers that can be delegated to?
warren at kumari.net
Fri Sep 12 13:22:47 UTC 2014
[ Note: I haven't had my morning coffee yet, this post likely rambling
/ incoherent... ]
What ever happened to the "let's use the glue as a service address"
trick? There was some drama about this a number of years ago, but it
died down, possibly as bandwidth and DNS became cheaper...
I cannot remember all the details, but basically I create a host
object (nameserver) named whatever the service I want to serve is --
so, if I have example.com, I register the nameserver as
'www.example.com', with the IP of my webserver, and now most of my
lookups are handled simply by the glue. I also run a nameserver on
that address, which has records for everything other than www (or
There were some issues (other than agility) that my caffeine deprived
brain cannot bring to mind, but...
On Fri, Sep 12, 2014 at 8:28 AM, Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote:
> On Fri, Sep 12, 2014 at 12:46:29PM +0100,
> Tony Finch <dot at dotat.at> wrote
> a message of 27 lines which said:
>> they have switched to a more standard EPP implementation.
> This is absolutely NOT "more standard". EPP allows both models (in
> other words, you do not have to implement RFC 5732).
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> dns-jobs mailing list
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
More information about the dns-operations