How do I configure slave name servers for my domains?

[rfl]

Hi everyone,

I just bought an account and I must say that I really like it, especially the fact that I can do everything by myself without asking anyone and waiting for help. Well, almost everything...

Before I signed up I read on the unixshell# website about the included DNS support: "What we will support: ... DNS - Customers may host as many domains as they want on our DNS servers for no charge."

But I'm not sure if I need to email support when I have my master name server ready to configure the slaves manually or maybe there is a way to add new zones using the Teknic or other frontend?

I see how to set up the reverse DNS but I can't find anything to add domains for slave name servers and I don't want to ask support unless I'm sure I can't do it by myself and it seems like something so common that it's probably automated.

So, does anyone know how to do it? Thanks a lot.

[matta]

E-mail support asking for your IP to be added as a trusted slave. Due to the DNS server we use any notifies received from your primary will automatically be added as a slave zone... of course if that is abused all entries will be removed.

[rfl]

[QUOTE=matta]E-mail support asking for your IP to be added as a trusted slave. Due to the DNS server we use any notifies received from your primary will automatically be added as a slave zone... of course if that is abused all entries will be removed.[/QUOTE]OK. Thanks a lot.

[goody]

[QUOTE=matta]E-mail support asking for your IP to be added as a trusted slave. Due to the DNS server we use any notifies received from your primary will automatically be added as a slave zone... of course if that is abused all entries will be removed.[/QUOTE]

I've had a ticket open for DNS slaving for three weeks and another for two weeks. Is there still a ticket backlog or did these get lost somehow?

[goody]

[QUOTE=goody]I've had a ticket open for DNS slaving for three weeks and another for two weeks. Is there still a ticket backlog or did these get lost somehow?[/QUOTE]

Help??!!??

[Al7zen]

[QUOTE=goody]I've had a ticket open for DNS slaving for three weeks and another for two weeks. Is there still a ticket backlog or did these get lost somehow?[/QUOTE]

same here !

[coolmacguy]

I've had one open for over a week so far. No response yet.

[werpon]

There are some free services such as ZoneEdit (http://www.zoneedit.com) or EveryDNS (http://www.everydns.net) that will let you use their nameservers, even as secondaries.

[matta]

Hi,

Sorry for the lack of updates, how our script adds the trusted zone seems to conflict with the web UI and then the primary/slave databases get out of sync. I should have this fixed by today.

[richardgreen]

Hi,

Is there anything I really need to do to bind to send notifies to ns1.unixshell.com? I have the following line in my zone file:

NS ns1.unixshell.com.

and also tried adding "notify yes" to the bind config but am not seeing any updates when I query ns1. Is there anything else I should do or should that work?

Thanks
Rich

[matta]

Submit a support ticket and then I can lookup the domain itself.

[goody]

[QUOTE=richardgreen]Hi,

Is there anything I really need to do to bind to send notifies to ns1.unixshell.com? I have the following line in my zone file:

NS ns1.unixshell.com.

and also tried adding "notify yes" to the bind config but am not seeing any updates when I query ns1. Is there anything else I should do or should that work?

Thanks
Rich[/QUOTE]

I'm seing the same issue. I tried "also-notify" for giggles and explicitly allowed ns1.unixshell.com in allow-transfer, to no avail. According to the Oreilly flying grasshopper book, an NS line in the zone file should be enough.

[coolmacguy]

Notifies are working just fine for me.

Here's my named.conf options config in case it helps anyone.

options {
directory "/etc";
pid-file "/var/run/named/named.pid";
notify yes;
allow-transfer {
65.254.53.9;
};
};

If you put that in options you don't need any domain specific options set, just use the regular

zone "yourdomain.com" {
type master;
file "/var/named/yourdomain.com.hosts";
};

Also you can tell if it's working by checking your system log. If it is you'll see something like this:

Jul 13 22:20:33 yourusername named[1588]: zone yourdomain.com/IN: sending notifies (serial 1121146786)
Jul 13 22:20:33 yourusername named[1588]: client 65.254.53.9#34177: transfer of 'yourdomain.com/IN': AXFR started

Also remember the usual things, you have to restard BIND after every DNS change for the new serial to be loaded and a notify to be sent. Also if you are running a firewall make sure to open port 53 on tcp and udp.

Hope that helps.

[richardgreen]

Hi,

Well I submitted a ticket about this a few days ago, looks like its ns1 at fault:

11-Jul-2005 23:49:13.865 zone atomic-x.co.uk/IN: notify response from
69.93.28.254#53: SERVFAIL

91.816759 72.9.242.242 -> 69.93.28.254 DNS Zone change notification SOA
atomic-x.co.uk
91.838750 69.93.28.254 -> 72.9.242.242 DNS Zone change notification
response, Server failure

Cheers Rich

[matta]

For a few of you guys it looks like it's trying to use 69.93.28.254 as ns1.unixshell.com. That hasn't been the IP for months now. The IP for ns1.unixshell.com is 65.254.53.9.

[coolmacguy]

[QUOTE=matta]For a few of you guys it looks like it's trying to use 69.93.28.254 as ns1.unixshell.com. That hasn't been the IP for months now. The IP for ns1.unixshell.com is 65.254.53.9.[/QUOTE]
When i run "dig ns1.unixshell.com" it returns 2 A records (both of those IPs). That's rather strange.

[matta]

Ahh... I think I caught an error during our conversion from BIND. It should be fixed now, might have to wait for the DNS cache of your resolver to expire. I already forced our primary resolver to reload.