I've got two servers hosted with a different company which used to act as my main DNS servers. After adding a few EV1 servers, I've decided to move the DNS to their own RHEL boxes at EV1 as well, and take down the older servers. While I was doing this, I decided to change my server naming scheme to a more "generic" structure, and changed the domain name.

Since I include domain registration for gTLD's with my service, I can update most of the domains that I host myself to use the new NS. However, a few domains that I don't control aren't responding to my email and are still pointing to the old NS.

Right now, all 4 servers have the same zone information with the exception of the NS records. What I'm wanting to do is move the old names to secondary IP's on the new servers, so that ns1.oldserver and ns1.newserver are on the same physical box, and similar for ns2.

My question is the content of the zone records. I've already got the zone files on the new servers, however they have ns1 and ns2.newserver for the NS records, not the old servers. Is this going to be a problem? Or do I need to change the NS records for each affected zone, and pray they notify me when they actually get around to changing their DNS server at the registrar so I can change it to the new server?

Or should I just get out a big stick and beat the unresponsive clients senselessly?

I think you can set up the old nameservers on the same ips as the new nameservers. Then change your old nameservers to point to the new ips.

http://forum.ev1servers.net/showthread.php...ervers+same+ips

Send the clients a message stating that the old nameservers will be discontinued at a certain date, then wait. What else can you do ?

alan

That helps, but I'm still a bit fuzzy on the zone file.

Would I need to set up NS records for both the old servers and the new servers, just the old, or would just the new work?

Right now, the zones on the old server still have:

IN NS ns1.oldserver

On the new server, I have a little script that cranks out the zone files how I like them, with the NS record pointing to ns1.newserver and ns2. Easy enough to modify it to put whatever NS I need to, but I'm not sure which one will work right.

And I've sent them 3 notices as of today - even after threatening service interruptions, they don't pay attention to them. I guess they think I'm joking. *shrug*

You shouldn't have to change any zone files for the sites concerned.
Are you shutting the old server down completely ?
If so, just create the records for ns1.oldserver etc on the new box and change the ns1.oldserver etc ips at your domain registrar. You will need the oldserver domain either pointed to the new box , or having the "new" ns1.oldserver etc ips in the A records for ns1.oldserver etc.

Is that understandable ?

I guess what I'm saying is you only need to change the ips for the oldserver nameservers to point to the new nameservers ips. The rest takes care of itself.

But you must (of course ) have A records existing for the oldserver nameservers, either on your new server, or on the old server pointing at the new server, depending on what you do with the oldserver.

LOL, it gets worse...

alan

That answers my questions

Yeah, I do plan on turning off these servers on the 13th, would like to cut the costs associated with them.

Thanks for your help, it's greatly appreciated.