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

Andris Kalnozols andris at hpl.hp.com
Mon Apr 14 05:31:45 UTC 2008


> Daniel Jonhson wrote:
> 
> 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


This was our situation when an HP Labs researcher registered a domain
with GoDaddy and wanted it hosted on HPL name servers so that we could
control things locally; the registrar said it could not be done because
the desired name servers were not registered with INTERNIC.NET.
In other words, GoDaddy effectively goes to the following site:

  http://www.internic.net/whois.html

and does a Nameserver search for the FQDN of the nameserver that you
want to use.  If it doesn't return a name and IP address, e.g.,

  Server Name:  LPANS5.HPL.HP.COM
  IP Address:   15.243.224.21
  Registrar:    MARKMONITOR INC.
  Whois Server: whois.markmonitor.com
  Referral URL: http://www.markmonitor.com

the name server update will be refused.  In our case, all it took
was a call to MarkMonitor and in a couple of days the InterNIC
registration was complete and GoDaddy had no problem with update
to the domain's NS records.

In your case, the IP address of `velolicio.us' does show up
in the InterNIC database but it is associated only with the
following two FQDNs:

  NS2.BACKSTREETMAFIA.NET
  NS2.HABBO-POSITIVE.COM

The name/IP address of `teknot.us' does not show up at all
with the InterNIC.

If you are not a customer of MarkMonitor, perhaps someone
else on this list would know how to get a name server
registered with InterNIC.

------
Andris



More information about the bind-users mailing list