Knowledgebase: Domains
Legacy DNS
Posted by on 11 October 2015 01:24 PM

Over the past couple of weeks we have migrated many of our servers to newer, more powerful hardware. As the migrations completed all traffic to the old server was being automatically routed to the new server. After the main name servers were updated the old were then switched off. This has caused problems for any domains that are set with legacy name servers or for domains using custom DNS. We have attempted to update as many of these old name servers as we can find so if you have had domains that were offline recently they may already be corrected. If you have a domain that is still down, double check the name servers that the domain is using. To determine the correct name servers for your hosting account

 

  • Go to https://www.arvixe.com/billing.php and Log in to our billing portal.

  • Click on hosting accounts to list your accounts.

  • Click on the hosting account to expand its details.

  • Look for the name of the server listed next to Server: for example lemur.arvixe.com

  • The correct name servers would then be ns1.lemur.arvixe.com and ns2.lemur.arvixe.com

  • If your server name begins with dallas and three digits such as dallas125

  • The correct name servers to use are ns1.arvixeshared.com and ns2.arvixeshared.com or for resellers ns1.mysitehosted.com and ns2.mysitehosted.com

 

If your domain is using custom DNS likely the IP address it is pointing to needs correcting. Follow the instructions above to determine what server your account is located on. Then navigate to

 

htttps://server-name/cpanel

 

for example : https://lemur.arvixe.com/cpanel

 

Once you login to the control panel, you will see your sites correct IP address listed in the column to the left of the page.

 

While updating your name servers should correct the problem the change does not take effect instantly. The new names servers will take several hours to propagate. If after 24 hours of making this change and your domain is still down, or the instructions provided here have not corrected your issue, please open a new ticket and use the following syntax for the subject so that we can respond to your issue as quickly as possible.

 

Subject : [servername] [account username] [main domain on account]

 

Provide as many details as possible including any error messages you are seeing and steps we can follow to reproduce the error if needed.  

 

(16 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).