LAST NIGHT the giant domain name registrar Register.com suffered an hour or two's worth of DNS problems.
The gossip on Twitter suggested that the company's name servers were the target of aDDOS attack, though this hasn't been confirmed.
Although DNS technical problems can be common, even for a provider is large as Register.com, the company has been rather unhelpful in disclosing any information regarding the outage - including complete denial from technical support staff.
This INQ hack holds several important domain names with Register.com and was interested in hearing reason's for the problems. But as you can see from the following chat transcript, Register.com tech support knew nothing of the outages, unlike the plethora of Register.com users on Twitter.
Jenny: Hello Dean.
Dean: Do you know if you had problems with service last night
Dean: Circa 8pm-10pm GMT
Dean: i.e. with your nameservers
Jenny: No, we have not faced any outage.
Jenny: Are you not able to access the website for your domain name?
Dean: no, we could not access several of the websites last night
Dean: our hosting provider indicated it may have been a nameserver issue
Dean: I am attempting to confirm with yourselves one way or another
Jenny: No, we have not faced any problem.
Jenny: And your website is pointed to hosting provider IP address.
Dean: er yes.
Jenny: And we have not faced any issues with other customers website.
One could presume from the last sentence that no other Register.com registered a support issue last night, despite all of the twittering on theblog-sphere.
It must be also noted, that in a prior technical support chat, we were plagued with sales attempts regarding our existing domains as opposed to any meaningful help.
The Register.com site doesn't appear to hold any current support information about problems or down-time, leading you to use one of their poorly-informed support staff.
Who knows quite what went on, Register.com support staff certainly don't. µ