Site Suggestions, Support and Resources > Tech Support and Forum Bugs

How to access TSP Forum if DNS is knocked out

<< < (3/3)

archer:
So yes, using the hosts trick or ip address trick will work with https. you'll just get complaints.

Hurricane:
Confusing, but thanks!

I.L.W.:
Maybe this will make it easier:

Windows 10 Users:
Right-click the Start Menu, select "Command Prompt (Admin)"
Click "OK"
If prompted, click "yes" to allow it to run.

Other versions of Windows:
Press [CRTL] + [Shift] + [Esc] to open the Task Manager
Go To "File" and "Create New Task" or "Run" (depending on your version)
Type "CMD" into the run box and check the box to start it as administrator. Click "OK" or "Run"


Paste the following into the command prompt and press [Enter]

--- Code: ---echo 206.190.141.186    thesurvivalpodcast.com    www.thesurvivalpodcast.com >> %windir%\system32\drivers\etc\hosts
--- End code ---

And again with this one:


--- Code: ---echo 206.190.141.187    survivalpodcast.net       www.survivalpodcast.net >> %windir%\system32\drivers\etc\hosts
--- End code ---


Next consider diversifying your DNS providers, such that if one is shut down, you have a fall-back DNS server in a different geographic location. It's not just protection from hackers. If a hurricane hits a server farm, it won't hit on opposite ends of the country simultaneously. If it does, you've got bigger problems than poor connectivity ;)

I like Google DNS as my primary, and OpenDNS as my secondary. These are open to the public, robust, distributed servers (not one central location), and they don't censor anything by omitting DNS records.

This can be changed in the command prompt as well.


--- Code: ---wmic nicconfig where (IPEnabled=TRUE) call SetDNSServerSearchOrder ("8.8.4.4","208.67.220.220")
--- End code ---

The likelihood of both of these getting DDOSed (attacked) at the same time is low. Additionally, the above code uses their backup DNS servers, which are unlikely to be a primary target.

For advanced users only:

https://dnscrypt.org/

A major source of security breaches and identity theft stems from "DNS leaks". As Archer pointed out, HTTPS works on he domain level. No connection between you and a DNS server is inherently secure. This means anyone can see what sites you go to, even if they can't tell what you do once you're there. Even Tor is susceptible to DNS leaks as they occur before primary routing of the secure traffic. This program encrypts your DNS requests, and will connect you to private DNS servers which support encryption. These private DNS servers, while admittedly less reliable and not as frequently updated are virtually guaranteed not to be the subject of mass denial of service attacks. Nobody's shutting down the guy with 1,000 users, they're going after big targets with millions of users. Even if they did target the little guy, the odds of them attacking the specific small server you're on are pretty remote.

A word of warning: Don't piss off your IT department at work using these techniques on a work PC. It can brake access to network resources in some corporate environments. This is for home PCs only.

Other things

Bookmark this page:
http://www.isitdownrightnow.com/thesurvivalpodcast.com.html

That will tell you if the TSP servers are down, or if the connection problem is on your end or with your ISP's ability to reach the TSP servers.

As long as you're mucking about in your hosts file, you can add the entries from the following site:
http://someonewhocares.org/hosts/

These are known scam sites, and creating a redirect to localhost (127.0.0.1) prevents your browser from going to them. A little bonus for online security if you're editing hosts anyway.

Navigation

[0] Message Index

[*] Previous page

Go to full version