Is godaddy wrong in disallowing using my domain as an NS server for itself?

[D. Stussy]

"Daniel Johnson" <teknotus at gmail.com> wrote in message
news:ftugp8$c6h$1 at sf1.isc.org...
> I'm trying to create a redundant DNS, and mail setup with the minimum
> number of IP addresses that passes all of the test suites I can find
> with no warnings.  So instead of having a typical ns0.domainname.net.
> ns1.domainname.net. my plan has been to use the domain names
> themselves as the host for each of the NS servers.  I've seen plenty
> of setups where the A record is something like
>
> domainname.net. IN A 198.x.x.x
> but the PTR record looks like...
> x.x.x.198.in-addr.arpa. IN PTR ns.domainname.net.
> or...
> x.x.x.198.in-addr.arpa. IN PTR mail.domainname.net.
>
> because they had to make the forward, and reverse records match for
> outgoing mail to not be blocked.
>
> This has always seemed ugly to me so the following is how I have stuff
> setup, but when I tried to change my domain registration to use my
> nameservers the control panel generated errors.  I submitted a ticket
> to tech support, and after it got escalated to their advanced tech
> support they said that my settings are wrong without going into any
> detail.  Is their control panel broken, and I'm getting burned as a
> result of buying cheap domain registration, or am I wrong?
>
> --------- My Setup --------
>
> $ dig @teknot.us teknot.us
>
> ; <<>> DiG 9.4.1-P1 <<>> @teknot.us teknot.us
> ; (1 server found)
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59724
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1
>
> ;; QUESTION SECTION:
> ;teknot.us.                     IN      A
>
> ;; ANSWER SECTION:
> teknot.us.              600     IN      A       67.207.129.28
>
> ;; AUTHORITY SECTION:
> teknot.us.              600     IN      NS      teknot.us.
> teknot.us.              600     IN      NS      velolicio.us.
>
> ;; ADDITIONAL SECTION:
> velolicio.us.           600     IN      A       67.18.208.127
>
> ;; Query time: 455 msec
> ;; SERVER: 67.207.129.28#53(67.207.129.28)
> ;; WHEN: Sun Apr 13 18:50:10 2008
> ;; MSG SIZE  rcvd: 97
>
> $ dig -x 67.207.129.28
>
> ; <<>> DiG 9.4.1-P1 <<>> -x 67.207.129.28
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54407
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;28.129.207.67.in-addr.arpa.    IN      PTR
>
> ;; ANSWER SECTION:
> 28.129.207.67.in-addr.arpa. 86400 IN    PTR     teknot.us.
>
> ;; Query time: 145 msec
> ;; SERVER: 10.11.3.193#53(10.11.3.193)
> ;; WHEN: Sun Apr 13 19:26:32 2008
> ;; MSG SIZE  rcvd: 67
>
> $ dig -x 67.18.208.127
>
> ; <<>> DiG 9.4.1-P1 <<>> -x 67.18.208.127
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33123
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;127.208.18.67.in-addr.arpa.    IN      PTR
>
> ;; ANSWER SECTION:
> 127.208.18.67.in-addr.arpa. 86400 IN    PTR     velolicio.us.
>
> ;; Query time: 199 msec
> ;; SERVER: 10.11.3.193#53(10.11.3.193)
> ;; WHEN: Sun Apr 13 19:25:51 2008
> ;; MSG SIZE  rcvd: 70

No, they are not wrong.  You are.  Although it has become popular practice
to assign an address to a domain name so that it can respond like a host,
there really isn't any RFC that suggests the practice.  Host names exist
within domains and name servers have host names.  (Name servers of this type
are what "glue" records are about).  Now, I shall admit that what you're
doing isn't exactly forbidden either, but it's not how things are done.