DNS system is back to normal!

[RichardK]

Hello All,

After a VERY long day of battling to get this back up, we are happy to report that our primary dns system is back to normal. That means any forwarding requests using this dns system are going through normally and without any delays. We are still trying to shore things completely from our end and will be installing fail safe measures to insure that this NEVER happens again or atleast to this degree. Rest assured, we will try our absolute hardest and will spare no expense to attempt to have our dns system running at 100% all of the time.

We will also be leaving the "back up dns" option available in your control panel from now on so that you will be able to easily switch from either dns system in case of emergency in the future. For those of you currently using our back up dns system, we ask that you remain there for a day or two. We are now adding the "switch back to our Primary dns" option to your control panel so you'll easily be able to switch back. Both dns systems are working fine so you should not be concerened about being on either.

I would like to take this opportunity from all of us here at NameCheap.com and and myself personally, to once again sincerely apologize for the extreme inconvenience this must have caused many of you and to thank you all very much for your patience you have shown throughout this very difficult time. We hope to not let you down again in the future and will be using every measure available to us to make sure of it. Either way, our entire staff and I are always here to serve you in any way way possible and to answer any of your concerns you may have both now and in the future. I personally I am at your disposal here to answer any questions for you and address any issues you may be experiencing. Please let me know if I can be of any help to any of you.

[derrin]

Well done Richard!d!!

I think it is important for us all now to not blame the victim. The nasty folks want us to leave Namecheap and go elsewhere. By leaving Namecheap we give them their victory.

I have had a horrible few hours and have lost the confidence of clients and end-users who are very important to me. BUT.... I will not be leaving Namecheap as a matter of principle.

The problems persist though and I need help. I am now on the backup servers and am getting a very flakey response. Sometimes the sites are working on one machine (but not on another), other times not. I have cleared cache, switched on and off and used a hammer on various machines.

I cannot work out why this might be happening. Can you clarify?

[lembregtse]

First of all thanks to the whole support and technical team for doing there best to get the DNS back working!

If I may suggest something?

Why not create an opt-in for users where they can choose to automatically change to the backup dns servers when there is a serious problem with the primary dns servers?
I think this would prevent allot of frustration and stuff. Or use a standard mixture of primary and backup nameservers so when one cannot be reached the other ones can? That's the point off multiple DNS entries I thought

Anyhow thanks again for the hard work!

[RichardK]

Thanks for the support guys.

Derrin, can you please pm me the details of your domain name and I will look into this for you?

[blackpudding]

Some of my domains are still unobtainable from this end and doing a DNS check returns the following:

dns verification:
Tried to fetch SOA record for domain, but DNS server dns2.registrar-servers.com [74.86.167.229] returned error code Server Failure
DNS server dns2.registrar-servers.com failed and will be dropped from other tests

mail-server check:
> 451 Temporary local problem - please try later
> Some of your MX do not work properly

Needless to say, traffic on the affected domains is at a fraction of it's normal level and income down to nearly zero.

I'll be glad when this is finally fixed. 24+ hours and counting

*EDIT* The sites are starting to reappear although some of the DNS servers are still reporting server failure.

[RichardK]

Some of my domains are still unobtainable from this end and doing a DNS check returns the following:

dns verification:
Tried to fetch SOA record for domain, but DNS server dns2.registrar-servers.com [74.86.167.229] returned error code Server Failure
DNS server dns2.registrar-servers.com failed and will be dropped from other tests

mail-server check:
> 451 Temporary local problem - please try later
> Some of your MX do not work properly

Needless to say, traffic on the affected domains is at a fraction of it's normal level and income down to nearly zero.

I'll be glad when this is finally fixed. 24+ hours and counting

Blackpudding, SOA records are not a normal requirement of nameservers. they are individual user specified settings but to do not affect normal url forwarding.

the same goes for MX records, they are user mail settings that indviduals would set up on their own in their host records.

Neither of the two reults you listed above would affect wether or not our forwarding servers are working correctly or not.

If you would like to provide your domain name, I can check it out for you.

[htl]

Richard, can I continue to use enoms name servers permanently?

[RichardK]

Richard, can I continue to use enoms name servers permanently?

Yes absolutely, the choice is yours.

[bytesback]

UPDATE: In less than a minute after I posted this, http://www.roseprojectfund.com started resolving from my work ISP again. If anyone at NameCheap did anything to correct this just now, THANK YOU!

I changed over to the backup DNS about 18 hours ago but I still can't resolve http://www.roseprojectfund.com (which is a URL forward) from my work ISP. Other ISP's I've tried seem OK. I was previously told that some ISP's take longer to see the change than others... but 18 hours?? Support just said to give it time...18 hours ago.

My real site domain is http://sites.google.com/site/roseprojectfund/ which resolves fine from my work ISP and any other I've tried. I do want to point out that the "www" is required on the beginning of my domain name http://www.roseprojectfund.com because Google Sites does not support naked links (i.e roseprojectfund.com).

Any help would be appreciated. http://www.roseprojectfund.com always came up fine on my work ISP before the DoS attack.

[coltpixy]

I still cannot get http://coltpixy.com My other domain took about 3 hours to propagate but this one still does not work after 16 hours. Any help would be much appreciated.