I have been researching the problems folks are having in Europe getting to ArtFire.com. I think we have found the root cause - but it is pretty technical so bear with me.
First an Internet lesson.
When you type in a web address you are really typing in a look up request for a number. Think of it like a phone book. You type in "Mr. Jones" but the phone has to call a phone number.
The same thing happens online.
You type in ArtFire.com but your computer really has to go to our IP address which is a number.
Now - if you call our number a lot your computer stores the number on your personal "phone book" but it checks the number every 20 hours or so.
To check it - it asks your ISP (Internet service provider) to look at its "phone book". The ISP checks to see if it has the number. If it does not (like the first time you go to ArtFire.com) the ISP calls a DNS (Domain Name Server) root server or hub. Think of that like a master phone book.
Now on to the problem
The European Hubs have changed the way phone numbers are written in the book. They did this because in some cases criminals could break into the phone book and rewrite the numbers. This was a way to steal money because they could make you think you were calling your bank when in fact you were calling them.
This hack was called DNS poisoning.
You can read about this change and the problems it causes here.
IF your ISP does not have the ability or has not made the adjustments to properly resolve this new "phone number" (DNS), you can't get to some websites . . . in this case ArtFire.com.
You can test this by clicking on the "phone number" for ArtFire above. While you will be able to get to ArtFire - you will not see images because those are still fed from a DNS resolver. If that is the case . . .
Here is what you need to do.
1) Call your ISP (Internet Service Provider) - the people who sell you your modem or internet access.
2) Ask to talk to tech support.
3) Tell them their DNS resolver is not working for ArtFire.com. Give them the IP address http://220.127.116.11/.
4) Tell them you suspect it may be due to the new DNSSEC protocol change on the DNS root servers.
5) Ask them to test for this and fix the issue or issue a refund for your interrupted service.
Expect them to not know what you are talking about or not believe you.
They are the only ones who can fix this. If you read the article you will find that it is the ISP that must properly resolve the new DNS protocol. We can do nothing on our end.
Please forward this to everyone you know has these problems, If you decide to contact your ISP hold firm, they will try to blame it on other things first and if you get a solution please let us know!