Registering nameservers - nice interface?
So I'll probably have various nameservers like ns*.mydomain.com where I'll need to register their IP with the root nameservers.
From my reading it apears that godaddy has an online interface that allows you to register/change nameservers IPs. Are there other registrars that do this (most seem to use a manual process)?
Alternatively I would be interested in commercial DNS providers that allow ns*.mydomain.com nameservers but I cant find any.
6 Replies
Alternatively, you can setup Zoneedit as a secondary DNS for your nameservers, and then just use zoneedit as your listed nameservers – sometimes termed a "hidden primary", if I remember correctly. That is you'd edit the zones on your box, and the changes would show up at zoneedit's nameservers, which is what everybody would use to query.
Or have I completely missed the point of your question?
Network Solutions however is more expensive than GoDaddy.
Hope this helps,
Good Luck!
Frank
ServerCentral has the same features on their web interface. you can change practically anything, including ns. Domain registering is $15/year …
Good luck
There are two issues
1. Every registrar has an interface to register name servers. But not every registrar has an interface for registering ns*.mydomain.com nameservers & IPs with root nameservers (for many registrars its a manual process, and I dont want that). Registering with the root namservers is needed to provide glue.
The post by areider1 is what I'm talking about
I've now verified (care of the above link) that godaddy is at least one registrar with an online interface interface allows you to do this.
2. I'd like to use an external DNS service for redundancy instead of running the sites & DNS server on one linode.
I use zoneedit for some some domains but I've got no idea about 'hidden primaries'.
After registering the domain and setting up DNS, there is an option to Add new dns servers to use or register DNS. If you select to register DNS then you will be prompted for the NS names. i used ns1 and ns2. No ip is requested as it will begin attempting to resolve the DNS of ns1 and ns2 to an ip on its own. As long as your DNS servers are set up with the proper DNS records, the Ip will resolve and boom you now have fully registered fully qualified DNS servers to do al the hosting for you.
Hope this helps,
Dan McIntosh
–--------------------------
Obective: set up a domain capriolepark.com, with nameservers ns1.capriolepark.com and ns2.capriolepark.com.
Environment: Redhat 9, firehol fiirewall, bind9 for DNS
1. Register capriolepark.com with godaddy.com
2. My linode IP is 64.5.53.79; order 2 more IPs for domain servers (using linode control panel) & get 70.85.16.70 & 70.85.16.71
3. In the godaddy control panel set:
Nameservers Summary:
NS1.CAPRIOLEPARK.COM
NS2.CAPRIOLEPARK.COM
Domain Host Summary:
NS1.CAPRIOLEPARK.COM
70.85.16.70
NS2.CAPRIOLEPARK.COM
70.85.16.71
4. "Domain host summary" is the most important bit; it registers the ns*.caproplepark.com nameservers with the root naameservers
5. Firewall: open port 53 in firehol
server dns accept
6. Set up bind with logging:
File:/etc/named.conf
options {
directory "/var/named";
};
logging {
category "default" { "debug"; };
category "general" { "debug"; };
category "database" { "debug"; };
category "security" { "debug"; };
category "config" { "debug"; };
category "resolver" { "debug"; };
category "xfer-in" { "debug"; };
category "xfer-out" { "debug"; };
category "notify" { "debug"; };
category "client" { "debug"; };
category "unmatched" { "debug"; };
category "network" { "debug"; };
category "update" { "debug"; };
category "queries" { "debug"; };
category "dispatch" { "debug"; };
category "dnssec" { "debug"; };
category "lame-servers" { "debug"; };
channel "debug" {
file "/tmp/nameddbg" versions 2 size 50m;
print-time yes;
print-category yes;
};
};
zone "capriolepark.com" {
type master;
file "capriolepark.com";}
;
File /var/named/capriolepark.com
$TTL 60
@ IN SOA ns1.capriolepark.com. root.capriolepark.com. (
200409218 ; serial, todays date + todays serial #
60 ; refresh, seconds
60 ; retry, seconds
60 ; expire, seconds
60 ) ; minimum, seconds
NS ns1.capriolepark.com.
NS ns2.capriolepark.com.
MX 10 mail.capriolepark.com. ; Primary Mail Exchanger
TXT "Capriole Park"
capriolepark.com. IN A 64.5.53.79
7. Start named (bind server) & examine logs:
Starting named: File /var/log/mesages
Feb 2 10:58:32 li-79 named[19392]: starting BIND 9.2.1
Feb 2 10:58:32 li-79 named[19392]: using 1 CPU
Feb 2 10:58:32 li-79 named[19394]: loading configuration from '/etc/named.conf'
Feb 2 10:58:32 li-79 named[19394]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 2 10:58:32 li-79 named[19394]: listening on IPv4 interface eth0, 64.5.53.79#53
Feb 2 10:58:32 li-79 named[19394]: listening on IPv4 interface eth0:1, 70.85.16.70#53
Feb 2 10:58:32 li-79 named[19394]: listening on IPv4 interface eth0:2, 70.85.16.71#53
Feb 2 10:58:32 li-79 named[19394]: command channel listening on 127.0.0.1#953
Feb 2 10:58:32 li-79 named[19394]: command channel listening on ::1#953
DNS requests come in: Log File /tmp/nameddbg:
eb 03 03:02:15.750 queries: client 203.194.56.150#39372: query: ns1.capriolepark.com IN A6
Feb 03 03:02:17.745 queries: client 203.194.56.150#39372: query: ns2.capriolepark.com IN A6
Feb 03 05:21:28.003 queries: client 216.145.1.3#32872: query:
Feb 03 05:21:29.030 queries: client 216.145.1.2#32843: query:
Feb 03 05:21:29.031 queries: client 216.145.1.3#32872: query:
Feb 03 05:22:40.647 queries: client 69.56.173.6#59764: query: ns1.capriolepark.com IN AAAA
Feb 03 05:23:06.746 queries: client 69.56.173.6#59764: query: capriolepark.com IN A
8: Note: DNS security will need to be tightened