If you prefer you can simply follow the RSS feed.
Server #2 went down around 7am. There is a problem with the hypervisor that it lives on and will be moved to a new host shortly.
I almost never use my dnscrypt.ca based XMPP address so I changed the contact page to show my snork.ca XMPP address. That way I only need to monitor a single account eh.
The host that runs Server #2 was down for a half hour around 6pm yesterday. When the host came back up the scripts I made were able to successfully restart all of the listeners.
Sorry folks, I screwed up the certs notification for routedns, so the doh services were barfing up an expired cert error. I have picked up fresh certs and they are running fine again. My bad!
The DNSSEC signatures expired today and as a result the dnscrypt.ca domain was not resolving properly for about 15 minutes. The resolvers were up and anyone already connected to them should not have noticed, but anyone initiating a new connection may not have been able to connect. Totally my bad. Sorry folks, I am going ot see if I can make a script that will automate signing (update BIND zone and reload domain) every second week.
I am expecting to switch from rebel.ca to 10dollar.ca in the next week or two. There should be no downtime [assuming DNS transfers fine] and if all goes well nobody will even notice. :-)
Someone recently alerted me to the fact that the provider-name and fingerprint information for the servers should be more readily available, so I changed the table on the main page to show a lot more information. All of this info can be compared against the public resolver list by using the dnscrypt.info stamp page.
Server #1 is moving to a new IP address (both IPv4 and IPv6). Most clients should automatically pull the new addresses from the public resolver list but see the main page if you need the details.
Curious eh? Well, have a look at the 2019 News.