Hey all..

always used ns1.domainname.com and ns2.domainname.com for all my domains on my w2k3/iis6 servers.

but I understand that I can also use The Planets dns servers too -- at [ns2.theplanet.com] and [ns1.theplanet.com]

is this a good idea? are there any problems for same? what then happens when I create a new domain on my server and it automatically creates their own DNS server items too?
do I just delete them or what?

problems? good idea?

?

Jim

Its good using TP's DNS due to their DNS servers being clustered, and in separate DC's.

If you add a domain to one of your servers, you'll have to submit a domain request via orbit so they can add it to their DNS servers.

Maybe TP could create some sort of API that would allow software to do this automatically? *hint hint*

I say if you have two or more servers, it's better to request one in a different datacenter form the first and run your own dns. Better branding, you have control, and you're not locked in now or in the future to relying on something else to update your dns.

We can also add slave entries to the named.conf so one could benefit from both control and the stability of our farm.

Hmmm...as I said, never used TP's nameservers....so I'm stuck I guess.

Have a domain on another TP server. Went to that domain Reg, and changed the ns there to point at ns1/ns2.theplanet.com -- instead of using ns1/ns2.domainname.com

Went to Plesk, created that new domain and then FTP'd in the files etc. All that is as normal.....done that a hundred times...

Tried then in Plesk to do a Site Preview - IE says can't find the site????

Is there anything else I need to do to get the TP ns to work?

oh yeah, have a ticket on this...but have other server issues to worry about right now....

sigh...

:-(

Jim

Did you go into orbit and add the domain zone for the DNS?

<grin> nope -- didn't know I had to. Figured Plesk my CP would do that for me....alas.....

anyways got it sorted....

thanks!

:-)

Jim

Tommy,

Could you please explain this a bit more?

Thanks,
Ryan