The Latest News
Connect with Us

Notable Releases
From the Store
Game of Thrones Stannis Baratheon Pint Glass
Game of Thrones Stannis Baratheon Pint Glass
Featured Sites
License Holders

Jump to content


Nameserver Change

  • Please log in to reply
1 reply to this topic

#1 Westeros



  • Root Admin
  • PipPipPipPipPipPipPipPip
  • 1,527 posts

Posted 02 October 2011 - 03:23 AM

We’re experimenting with a new nameserver host for all sites. We’ve switched to Cloudflare, which uses its nameservers to cache static content (images, scripts) on its servers distributed across several continents, and to serve that content from the server nearest to the user. This should, in theory, improve site performance and marginally improve server load, as the server will spend less time pushing images and scripts and have more time to churn through the database which powers Westeros-proper, the wiki, and the forum.

For most of you, this change should happen in the background and will require no action from you. However, in some cases your ISP’s domain name server may change in an incorrect fashion, or your own computer may be holding on to outdated information. This may lead to your not being able to reach some Westeros sites but not others.

In this case, we recommend flushing DNS on your computer (if on a Windows PC: Start -> Run -> cmd -> ipconfig /flushdns; for Mac OS X users, please see this.) That should correct the problem in many cases. If your own ISP's name resolver is at fault, usually they will update their records in anything from 2 to 4 hours. Please be patient and try again after that time (making sure to use ipconfig /flushdns again).

If problems persist, please e-mail [email protected] and we’ll try to help you resolve them.

Visit the Site!

Edited by Ran, 02 October 2011 - 06:16 AM.

#2 Calibandar


    Herald of Winter

  • Members
  • PipPipPipPipPipPipPipPip
  • 7,712 posts

Posted 02 October 2011 - 05:31 AM

At last, access again. I lost access to the forum yesterday, whereas and the wiki remained available.

I checked all possible settings on my computer for a few hours, from scanners to firewalls, but coudln't find what it was. Seeing this message on another computer and flushing DNS on my own immediately solved it.