Iceland went down this morning due to a kernel panic in the kworker process.
We're still looking into the cause behind this crash, but as of now the system is back online and all services there are running normally.
Ξ welcome to cryptostorm's member forums ~ you don't have to be a cryptostorm member to post here Ξ
∞ take a peek at our legendary cryptostorm_is twitter feed if you're into that kind of thing ∞
Ξ we're rolling out voodoo network security across cryptostorm - big things happening, indeed! Ξ
Ξ any OpenVPN configs found on the forum are likely outdated. For the latest, visit GitHub Ξ
∞ take a peek at our legendary cryptostorm_is twitter feed if you're into that kind of thing ∞
Ξ we're rolling out voodoo network security across cryptostorm - big things happening, indeed! Ξ
Ξ any OpenVPN configs found on the forum are likely outdated. For the latest, visit GitHub Ξ
Iceland went down this morning (it's up now)
-
marzametal
- Posts: 499
- Joined: Mon Aug 05, 2013 11:39 am
Re: Iceland went down this morning (it's up now)
woo hoo... !!!
What happens when it goes down again? For example, I use 79.134.235.131 and .132 as my DNS entries in Router and Windows config...
From what I understand (most likely wrong... lol), other DNS entries from other exit nodes are "pushed", the above two are always active...
What can I replace them with to get onto CS if Iceland goes down again?
What happens when it goes down again? For example, I use 79.134.235.131 and .132 as my DNS entries in Router and Windows config...
From what I understand (most likely wrong... lol), other DNS entries from other exit nodes are "pushed", the above two are always active...
What can I replace them with to get onto CS if Iceland goes down again?
Re: Iceland went down this morning (it's up now)
Actually, all the other deep DNS IPs are public just like fenrir's. They're "pushed" yea, but you don't have to be on the VPN to use them. So any of these can also be used:
103.254.153.244
109.71.42.228
198.100.159.249
198.204.245.3
212.129.46.32
212.129.46.86
31.24.34.50
46.165.222.246
76.164.234.11
91.214.70.199
The same list is @ https://github.com/cryptostorm/cstorm_s ... NS_IPs.txt but keep in mind that one day we're probably going to make the above IPs private (for on-VPN use only) but also setup some new resolvers that are public only.
103.254.153.244
109.71.42.228
198.100.159.249
198.204.245.3
212.129.46.32
212.129.46.86
31.24.34.50
46.165.222.246
76.164.234.11
91.214.70.199
The same list is @ https://github.com/cryptostorm/cstorm_s ... NS_IPs.txt but keep in mind that one day we're probably going to make the above IPs private (for on-VPN use only) but also setup some new resolvers that are public only.
-
marzametal
- Posts: 499
- Joined: Mon Aug 05, 2013 11:39 am
Re: Iceland went down this morning (it's up now)
Cheese for the info DF...
Re: Iceland went down this morning (it's up now)
Cheese? I like cheese...
But yea, deep dns IPs are public. You can use them for anything that's normal DNS.
The main thing with those IPs is that if you're on CS, they will automagically translate .i2p and .onion transparently so for people on CS that means transparent .onion and .i2p access (along with a few other non-internet domains).
.onion seems to work across the board. i2p is a little more flakey, but it mostly works.
But yea, deep dns IPs are public. You can use them for anything that's normal DNS.
The main thing with those IPs is that if you're on CS, they will automagically translate .i2p and .onion transparently so for people on CS that means transparent .onion and .i2p access (along with a few other non-internet domains).
.onion seems to work across the board. i2p is a little more flakey, but it mostly works.
Return to “cryptostorm in-depth: announcements, how it works, what it is”
Who is online
Users browsing this forum: No registered users and 5 guests