[dns-operations] go daddy refuses to register NS not otherwise associated with go daddy controlled domains
m3047 at m3047.net
Wed Sep 12 20:00:19 UTC 2012
On Wed, 12 Sep 2012, David Conrad wrote:
> If I'm interpreting this correctly (i.e., "CNAME at zone apex"),
Yes. One of the common things people do is to configure their nameservers
with that very CNAME. Why should they go to that trouble (to do it wrong,
at that), why can't the delegator just do that?
> what they're supposed to do is allow folks to (e.g.) have example.com,
> example.org, etc. point to www.myhostingservice.biz. My impression is
> that they're supposed to work by returning the CNAME if the answer isn't
> in the zone data. That is, if you have:
> $ORIGIN foo.com.
> @ IN NS ns.nsservers.com.
> IN MX 1 my.email.com.
> IN CNAME mysite.hostingprovider.com.
You have the general idea (although I think it violates the "nothing but a
CNAME at a node" guideline). Based on what I see in the wild I'd settle
for just the CNAME for the domain. Wildcarding it would be fantastic, and
anything beyond that is Santa Claus and the Easter Bunny.
More information about the dns-operations