You just can’t win

I’m currently trying to report an issue with my VPS. I can’t though because ServInt’s support site is down.

Seriously, why is it so hard to find a reliable host?

I was moving away from PowerVPS as I’ve had a few problems with them recently including hostnames and root passwords mysteriously changing in the middle of my trying to set up my new VPS. But I’m not getting any further with ServInt. Bare in mind that these are the two most well respected VPS companies in existence. So it’s hard to draw any conclusion other than than I am cursed.

Consider some of the fun problems we’re currently tackling. Most of the websites in the network use nsx.mazedev.com as their nameservers. These are registered with the domain registrar and so are seperate to the server which hosts mazedev.com itself. Yet if you take that server offline, all domains that are not .com or .net (such as .co.uk, .info and .org) stop resolving. Yep, get your head around that one.

Meanwhile I still can’t get any work on my project done, run my website backups or generally access anything at Burchett Place because of our connectivity issues. The replacement modem was supposed to arrive today, after all I ordered it middle of last week and payed for next day delivery. It hasn’t turned up. I can’t phone City Link because eBuyer haven’t given me a consignment number and I can’t phone eBuyer because they are closed for new year.

This results in me not being able to go home and do some revision because I need to be here with internet access to resolve these issues I am having with all the websites which is now starting to cost me lots of money, money which I don’t have. Still, who really wanted a degree anyway?

Metadata

This entry was posted on Monday, December 31st, 2007 at 3:27 pm and is filed under Life, Rants, Tech, Thoughts. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “You just can’t win”

  1. Kieran O'Shea Says:

    Surely nsx.mazedev.com will point to some nameserver or other, usually of the Linux variety running bind. These servers will hold the authoratitive records for your domains, most likely pointing them to a whole load of servers, vps systems and reseller accounts. Where are these bind server(s) located? Any chance they are located on the server hosting web (and other) content for mazedev.com? I certainly wouldn’t be surprised as this is a very common setup. If this is the case, it would explain why bringing it offline causes the resolving to fail.

    Sure, your registrar may well hold records for nsx.mazedev.com and IPs of where these domains point but these IPs need to be to servers that are up and authorativiely answering for the domains that have nsx.mazedev.com as their primary nameserver.

    Just a thought from a webhost anyway ;)

  2. Chris Worfolk Says:

    The nsx.mazedev.com addresses are pointed to the BIND servers on the VPS’s themselves, seperate to the VPS hosting mazedev.com.

    Luckily I’ve got replies back from both my registrar and my server company. NameCheap have explained that it’s a problem with the server and the server companies have said it’s a problem with the domain registrar. Fantastic stuff.

    What is really puzzling though is why .com and .net domains work fine but the others don’t. Do they have different rules with regards to nameservers?

Leave a Reply