I got theplanet to set up as a slave dns for me and they msged me this:

DNS slaving has been configured for the domain addictedhosting.com. Please configure your DNS to allow zone transfer request from 12.96.161.249.

now how do I allow zone transfer request? cpanel has a cluster function for something like this, but I am assuming they have to be running cpanel also inorder for it to work. is there another way to allow zone transfers, and how?

so far what I have been reading I do not need to make any changes to master inorder for slave to work... can anybody confirm this please?

As far as I understand it, the way it normally works is that whenever you update the master DNS, it sends a notification to the slave, and then the slave just updates itself. So no changes are needed on the master.

Maybe TP servers work differently? I guess using requests from the slave (which could be set to occur less often to reduce traffic) may be implemented by TP?

HTH,
Matt

Ahh... so you have bind running on your server so that additions to dns are added to the local dns quickly (with cpanel or whatever), and then are sent to SM's nameservers?

That's what I want to do... it keeps from having to make a ticket for each domain in orbit, or having to manually update their dns for subdomains, etc.

This is what they replied back to in my ticket:

If you would like, we can configure your BIND through SSH to allow zone transfer for the domain mydomain.com to 12.96.161.249.

Now I just gotta wait for OS reload to finish and have them set that up

No... first of all I run DirectAdmin rather than CPanel. I run my slave DNS on a seperate box to mirror the master DNS on my DirectAdmin box. It requires no changes to be made on the main DA box.

HTH,
Matt

Shanlar: (and anyone else who has Tp's nameservers as slaves, or who knows how to fix this problem)...

The Planet's nameservers are both lame for me... not responding authoritatively for my domains... and they are also allowing recursive lookups from anyone. (according to dnsreport.com) Are you nameservers all working properly? How did you set them up?

I had support set them up as dns slaves to my primary... so are the two issues above from my configuration or theirs? I think the recursive lookups setting is a named.conf setting that doesn't transfer to the slaves.

I do have my ns2. and ns3 nameserver names going to their ip #'s... i wonder if that could be a problem... I'm not sure how though because I think they should just be copying my entire zone which works fine. My primary nameserver doesn't have any issues. I've denied recursive lookups for anyone but local ips... and it answers authoritatively for my domains.

Any suggestions? I would contact support but I hate to bug them if it's my fault that it's not working properly.

What you need to do is add the line:


or what ever the IP address(es) they gave you to your named.conf file in the options section. That is all I have done, and all my domains are resolving fine on their DNS servers.

Toml,

Can you check your dns at http://www.dnsreport.com and let me know if theplanet's nameservers that you have as your secondaries (slaved) pass the Lame nameserver test or not?

Because they are not returning the -aa (authoritative) bit for any of my domains... and the tech's comment on the ticket I opened said that this was a normal thing for secondaries to do... however, I use zoneedit.com as secondary nameservers for some of my domains as well and they are set to slave from my primaries and those nameservers properly return the authoritative bit for the domains they are secondaries for. thanks.

You are correct, some of my domains don't have a problem, but others do. It would appear as though all the domains I added after I had them slave off my DNS server are reporting theirs as Lame. I remember testing this at one time and it appeared to work. I will have to investigate this a little further.

they informed me that the slave only works for domains that you have sent a domain ticket to them for. so basically slaving with them is useless unless you dont care to send in a ticket for every new domain

im gonna have to find another reliable server to slave with.

Yeah... that's what I've suspected too... (except they haven't actually gotten around to updating/answering my ticket yet).

I understand the security issues with allowing just anyone to tell their nameservers about any domain though... I don't think i'll mind so much if I have to send in requests for new domains to be added before they'll appear in the dns if I don't have to do anything after that - ie automatic slave transfers. It was manually managing the domains, and their subdomains, etc manually in Orbit that I was having a problem with.

I suppose that several of us could get together and swap slave nameservers from our own servers... (I think it's just a onetime setup to get it all the slaves going, then basically automated transfers from there). I've got some security improvements done to my Bind config... like disabling recursion and zone transfers for all except trusted hosts... and if I was to be involved I'd like the others to do that as well, but those changes really aren't hard to do.

I had to tell them which IP my server was on so they could setup their slave DNS, so it is not like any old server can update their DNS. And having to require a ticket for all domains that I add is not too bad, but then I need to watch every domain my resellers add/modify to resend a tickent. That does not sound right, they should have told me they didn't do slaves.