(05-01-2017, 03:26 AM)Inori Wrote: Recently, a lot of people (myself included) have been having intermittent problems with connecting to Sinisterly because of failed DNS lookups. If you're unfamiliar with that term, you might recognize this kind of error message:


I haven't fully figured out why this has been popping up so much recently (speculation points to outdated DNS provider caches and such), but I figured out a fix. As many people on Discord have pointed out, flushing your local DNS and clearing your browser's cache can help resolve the issue.

Clearing your browser cache is usually done by going to Settings > Advanced > Clear Browsing Data or something similar and checking the appropriate "Cached images and files" box.


Flushing your DNS cache can be a little more difficult. The commands below need to be run in the Windows command prompt, Linux shell, or OSX terminal, respectively.

Spoiler: snippets

Windows

Code:

ipconfig /flushdns

Linux (some Debian distros)

Code:

sudo service dns-clean restart

Linux (Other)

Code:

nscd -I hosts

OSX

Code:

dscacheutil -flushcache;sudo killall -HUP mDNSResponder

If none of the above methods fix your connection problems, changing your router's DNS lookup servers could help. Depending on your router, the control panel will be on the local IP 192.168.2.1 or similar (just type it in the URL bar of a browser as you would a website address; google your router model if you're not having any luck), and the user/password combo is often admin/admin (again, google if you're not sure).

Read your manual or the online documentation, but there should always be a page to configure DNS. If it's set to "Obtain DNS information automatically" or something like it, change it to manual and use a public resolver like Google or OpenNIC.