Server Issues Today

[Mark]

If anyone had problems posting today it was because of a fault with the database configuration. I have resolved this now and all should hopefully be well.

 

Sorry for the inconvenience.

[clockboy]

Well done Mark much appreciated

[Geo]

I slept in so missed the problem!

[bobm12]

No problem here either!

[Mark]

Another problem with Cloudflare today. Things are a bit slow. It's a bugger to be honest.

 

Update - Removing congestion from IAD. 
Feb 12, 20:32 UTC

Update - We are actively working on alleviating network congestion in some of our European datacentres. 
Feb 12, 19:59 UTC

Identified - The issue has been identified and a fix is being implemented. 
Feb 12, 08:50 UTC

Investigating - We are investigating network issues in Frankfurt, the colo has been rerouted. 
Feb 12, 06:29 UTC

[Geo]

All I do is say thanks Mark, it's way over my head.

[Mark]

Cloudflare has had a lot of problems recently - I wonder if it has anything to do with them providing CDN for the pirateBay. If it carries on then I will stop using the CDN.

[Mark]

Seems to be faster now. Hope it stays that way.

 

[clockboy]

I have noticed sometimes it takes a little while for new post to save. This is the issue I presume.

[Mark]

Don't think so - mainly referring to the general slowness of the site a few days ago. It should all be resolved now.

 

I have taken my other site off cloudflare to see what difference it will make before I make a decision about WRT. hopefully it will be better from now on.

[Rob]

I couldn't access the site today because the host didn't resolve… I'm using Google's dns and checking the domain gives a SERVFAIL error:

# dig www.watchrepairtalk.com @8.8.8.8              ; <<>> DiG 9.8.5-P1 <<>> www.watchrepairtalk.com @8.8.8.8;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15544;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:;www.watchrepairtalk.com.	IN	A;; Query time: 55 msec;; SERVER: 8.8.8.8#53(8.8.8.8);; WHEN: Mon Mar 09 12:37:31 CET 2015;; MSG SIZE  rcvd: 41

One possible reason for this error is that the DNSSEC configuration is broken.

[Geo]

I've been on and off the forum a few times this morning without any issues whatsoever.

[clockboy]

Same here no issues to report..

Edited March 9, 2015 by clockboy

[WillFly]

I've just uploaded a dozen or so worksheets - no problems.

[Mark]

I just changed my computers DNS to use google's - will report back if I have problems.

[Mark]

Access was very choppy with googles DNS servers (8.8.8.8 and 8.8.4.4)

In fact it was for several domains I visited.

 

Changing back to the BT DNS servers and all is fine.

 

I did a check http://www.intodns.com/watchrepairtalk.comand all seems fine with the DNS records (the two errors stated are beyond my control and do not cause errors for DNS queries for A and MX records).

 

 

Checking further I find that it is a problem for some domain owners who use the Google DNS service: https://groups.google.com/forum/#!topic/public-dns-discuss/7Dd4pzBfpZA

 

As it is - I find nothing to fix but will keep monitoring just in case.

 

Thanks for reporting Rob.

[Rob]

Further investigation points to DNS problems at the eNom registrar.

 

Maybe Google's dns is quicker to propagate the issues, and that's why I noticed it there first. In any case, there's not much Mark can do to fix it, we'll just have to ride it out. 

[Mark]

Well done for finding that Rob.

I did look on the service status page at eNom but didn't see any issues, the article explains a lot.

 

If it happens again, I will look into deploying my own secondary DNS. It's a shame - I was using eNom's DNS service specifically to reduce admin overhead. Mind you - i've been with them for many years and the provided DNS service is usually quite stable.