Discontinuing Nameservers

**NexDog** · 03-31-2011, 07:40 AM

We are discontinuing a few old nameservers on our Linux servers. Basically all the "control-access.com" nameservers are being discontinued and you need to make sure you are using the "dns-shield.com" nameservers.

========================
ARIES

ns11.dns-shield.com
ns12.dns-shield.com

DISCONTINUING
ns.control-access6.com
ns2.control-access6.com
ns.control-access10.com
ns2.control-access10.com

========================
TAURUS

ns13.dns-shield.com
ns14.dns-shield.com

DISCONTINUING
ns.control-access3.com
ns2.control-access3.com
ns.control-access12.com
ns2.control-access12.com

========================
CANCER

ns15.dns-shield.com
ns16.dns-shield.com

DISCONTINUING
ns.control-access4.com
ns2.control-access4.com
ns.control-access16.com
ns2.control-access16.com

========================
LEO

ns17.dns-shield.com
ns18.dns-shield.com

DISCONTINUING
ns.control-access.com
ns2.control-access.com
ns.control-access14.com
ns2.control-access14.com

========================
VIRGO

ns19.dns-shield.com
ns20.dns-shield.com

DISCONTINUING
ns.control-access2.com
ns2.control-access2.com
ns.control-access11.com
ns2.control-access11.com

========================
BETA

ns23.dns-shield.com
ns24.dns-shield.com

DISCONTINUING
ns.control-access7.com
ns2.control-access7.com
ns.hostnexus7.com
ns2.hostnexus7.com

========================
ZETA

ns25.dns-shield.com
ns26.dns-shield.com

DISCONTINUING
ns.control-access5.com
ns2.control-access5.com

========================
THETA

ns27.dns-shield.com
ns28.dns-shield.com

DISCONTINUING
ns.control-access9.com
ns2.control-access9.com

========================
OMIKRON

ns29.dns-shield.com
ns30.dns-shield.com

DISCONTINUING
ns.control-access8.com
ns2.control-access8.com

========================

We are just letting these domains expire over the next year with the first domains expiring end of May so please make sure you change nameservers within 2 months to avoid any issues.

BillSamuel · 03-31-2011, 09:11 PM

I believe I'm using the ones discontinued. For those of us who don't have a lot of technical knowledge, could you explain what all we need to do to switch to the new ones?

**NexDog** · 03-31-2011, 11:33 PM

Yep, pretty simple. Just identify the nameservers you use in the list and under that Server's entry see the dns-shield.com nameservers, they are the ones you'll need to use. Then login to your registrar and change your nameservers to the dns-shield.com ones and you're good to go.

BillSamuel · 04-01-2011, 09:24 AM

What about at the hosting end? They are also listed in Plesk, and in fact the address for Plesk seems to be based on it. I access Plesk through https://www.control-access14.com:8443. Does this all change automatically when the changes at the registrar propagate? What would be my new Plesk address based on the ns17.dns-shield.com?

**NexDog** · 04-01-2011, 09:30 AM

Easisrt way to remember Plesk URL:

https://www.QuakerInfo.com:8443

All the domains in your signature use NS17.DNS-SHIELD.COM and NS18.DNS-SHIELD.COM so you won't need to make any changes. So just update your bookmark for Plesk and you're all set.

BillSamuel · 04-01-2011, 10:00 AM

I had no idea I could access all my domains by using the address of just one of them, but I tried it and I can. But when I go into Plesk, I find my DNS server settings are still at the old control-access14 ones. Will these self-correct eventually or should I go in and edit them?

j-z · 04-01-2011, 12:08 PM

On a somewhat related topic: there is still the need for the security exception when using these URLs. I'm writing to tell my clients of the change (about 10 or so) and I am going to have to tell that that even though their browser is freaking out about a security risk it's really not a big deal. And then how to jump through the hoops to add a security exception on all the major browsers. Am I the only one who feels this is awkward? Am I missing something here?

BillSamuel · 04-01-2011, 02:06 PM

It is awkward. It does raise questions.

**NexDog** · 04-01-2011, 11:15 PM

Quote:

Originally Posted by j-z

On a somewhat related topic: there is still the need for the security exception when using these URLs. I'm writing to tell my clients of the change (about 10 or so) and I am going to have to tell that that even though their browser is freaking out about a security risk it's really not a big deal. And then how to jump through the hoops to add a security exception on all the major browsers. Am I the only one who feels this is awkward? Am I missing something here?

After 7 years you'd think you'd be used to that.

You only need to change the URL if your login URL contains "control-access.com". Most people use the IP and it's the IP URL that we put on our Activation emails. You add the exception once and you're pretty much done for life. Still, it does get reset on some Plesk upgrades and on some servers we have requests to install self-signed certs each year. I guess I could install a wild card SSLL cert for "*@dns-shield.com" so people could login at "https://leo.dns-shield.com:8443" etc.

Bill, you can edit the NS records in Plesk if you like but generally it's not really needed. DNS purists would argue with me though. So in Plesk, just click on the NS record and change it to the new one if you like.

buteverde · 04-02-2011, 08:50 AM

Thanks for asking the important questions, Bill. And Laurence, there for us as always.

Maybe things have changed since I first had to learn about DNS, but wasn't there something about after having posted the DNS numbers, there would be a time of "circulating through the web" or some such?

Also it seems odd that I can just go into the registrar and change the numbers and there is no effect on the access to the sites?