[dns-operations] go daddy refuses to register NS not otherwise associated with go daddy controlled domains

David Conrad drc at virtualized.org
Wed Sep 12 20:45:22 UTC 2012

On Sep 12, 2012, at 1:00 PM, Jan-Piet Mens <jpmens.dns at gmail.com> wrote:
>> $ORIGIN foo.com.
>> @ IN NS ns.nsservers.com.
>>  IN MX 1 my.email.com.
>>  IN CNAME mysite.hostingprovider.com.
> No CNAME and other data -- that is illegal. (c.f. [1] :-)
>        -JP
> [1]: https://twitter.com/dns_borat/status/141872826536837121


I had a "P.S. Yes, I know CNAME at zone apex is illegal, I'm merely responding to Andrew's question" in my message but figured no one on the dns-operations list would think anyone on the list wouldn't know this.  My bad.

Yes, I'm quite well aware that CNAME and other data is illegal, thanks. However, non-DNS people see value in it, configure it, and then get quite unhappy when various rare applications (e.g., Microsoft Exchange) get confused. Quoting RFCs at folks, particularly when there are (arguably) reasonable unambiguous ways in which it could be implemented, typically generates more unhappiness. So it goes.


More information about the dns-operations mailing list