The Planet Forums > Using SM dns servers as slaves

Full Version: Using SM dns servers as slaves

The Planet Forums > System Administration > DNS Hosting

Sam Bauers

Mar 9 2005, 09:16 PM

I want to set up my own DNS server as the master for all my domain name administration, but I would like to use ServerMatrix's domain name servers as slaves.

Before I make a request in Orbit, I want to know if anyone out there is doing this now and if it has worked out for them.

dezignguy

Mar 10 2005, 03:29 AM

yup... it works great. I have my primary running on my server, and the two planet NS are my slaves. :twisted:

Though you will have to open a ticket for new domains to be setup with the slave zones. If you were using SM's dns through Orbit though, you'd have the same thing though, so it's no extra trouble. And once they're in there, then the dns data will get automatically updated from your primary. It's a great setup.

Sam Bauers

Mar 11 2005, 07:34 AM

I'm having a real hard time getting this request through.

I thought it would be simple, but the guy at the SM end doesn't seem to get it.

What should I be asking for?

Here's the thread (with some details x'ed out).....

QUOTE

Domain: xxxxxxx.net.au
Change: Please setup slave records for this domain on the sermatrix domain name servers. I will be running the master record from my server.

Primary (my server): 70.85.xxx.xxx
Secondary (ns1.servermatirx.com): 216.185.111.10
Secondary (ns2.servermatrix.com): 69.56.222.10

The zone on my server has been setup to allow zone transfers to these servers

Thanks.
------------------------------------------

(aallen-03/11/2005 05:58:23):
What ip address do you want network.net.au to point to?
--------------------------------------
(xxxxxxxx-03/11/2005 06:24:49):I don't want you to add specific records at all, I have already set up the full zone on my server that will contain those details, I just want the servermatrix dns servers to replicate that zone.

If the servermatrix servers are set up as slaves to the Primary server at 70.85.xxx.xxx (my server) then this should occur automatically.

Is this possible?

Thanks, Sam
------------------------------------------

(aallen-03/11/2005 06:56:29):
Right now, your server 70.85.xxx.xxx nameserver is set as

1st DNS: 216.185.111.9
2nd DNS: 216.185.111.10 (ns1.servermatrix.com)

--------------------------------------
(xxxxxxxx-03/11/2005 07:29:14):I don't think you are understanding my request.

I am running a DNS server on 70.85.xxx.xxx

On that DNS server I have created a domain zone "xxxxxxx.net.au"

I want that zone to be the authorative primary or master zone for the domain "xxxxxxx.net.au", (which it is now set up to be).

I want the ServerMatrix DNS servers at ns1.servermatrix.com and ns2.servermatrix.com to be set up (by you) as the secondary or slave servers for the domain name "xxxxxxx.net.au".

This way, I can change DNS settings on my server (the master) and they will automatically propogate to your DNS servers (the slaves).

If you were running BIND then the entry into named.conf on YOUR servermatrix DNS servers would be something like...

zone "xxxxxxx.net.au" {
type slave;
file "path/to/slave/records/xxxxxxx.net.au.dns";
masters { 70.85.xxx.xxx; };
};

Sam

riziko

Mar 13 2005, 09:23 PM

Well I also had a lot of trouble getting SM to setup a secondary dns entry. I was amazed at how difficult it was. It is kinda like induction into a secret society.

WHAT THEY DON'T TELL YOU
As I understand it, the way it works is that the 4 nameservers (ns1 & 2 for theplanet.com & servermatrix.com) run the same set of records. The zone transfers occur from a different server - 12.96.161.249 (ns0-admin.theplanet.com), so you must allow zone transfers to 12.96.161.249 for it to work. The zone transfers don't occur from the 4 nameservers.

This is the assumed knowledge that is not written down anywhere but you just have to open a few tickets to find out. I wish SM would document it somewhere!

Ross

dezignguy

Mar 14 2005, 10:08 AM

ahh yes... I think I discovered that by checking my logs and finding that that ip was constantly trying for zone transfers. Looking up the reverse dns made it obvious that it was an sm admin ip that I needed to allow for zone transfers.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.