http://status.ucann2.net/ and http://status.ucann2/ is now operating as expected, and displaying all nameservers response times.
If you are looking to check an individual structure, please use the following links, as http://status.ucann2/ uses javascript to pool the servers and display on the main page.
Some time ago, (July/June 2017), verelox.com had an infrastructure issue, where the crt.dist.dns.ucann2 (public CRT DNS) was shutdown. After a short time, the crt.dist.dns.ucann2 public server was activated, however networking connection failures continued. After some digging into the issue, and many attempts to update this server to be constant and up to date, it was determined yesterday (9-12-2017), to shut down the DNS services. Those using the crt.dist.dns.ucann2 server as one of their public resolver will see some latency until a change to the nameserver configurations can be made. UCANN2 is in communications and working with CRT to update all servers to use crt2.dist.dns.ucann2 (a server to replace crt.dist.dns.ucan2 at time of incident [above]).
UCANN2’s infrastructure is already operating at peak efficiency, and CRT’s infrastructure is operating as expected, and CRT and UCANN2 continue to monitor all DNS services.
Please see below the new name server IP addresses.
Please see the below links to follow up on exactly what happened with the verelox.com infrastructure and services.
Due to unforeseen issues, Cesdian Root (CRT) had an issue with their United States (US) homed servers. We at UCANN2 decided to jump in and lend a helping hand. UCANN2 is proud to announce that we are now a n active sponsor of Cesidian Root (CRT). We’ve spun up four clusters around the United States to provide constant, stable and reliable US resolving for CRT. Here are the new servers:
UCANN2 and CRT have been working around the clock to adjust the configurations of all UCANN2 and CRT DNS servers, and are now proud to announce, all services are operating at 100% and DNS is resolving faster then ever.
You can download the latest named.db from https://www.cesidianroot.eu/downloads.html and the new Server List from https://www.cesidianroot.eu/generic.html
UCANN2 and CRT are always looking for reliable and stable sponsors, if you are able to provide sponsorship, please give us a shout, simple send an email to [email protected] or [email protected]
If you are looking for more to your internet experience, simple change the DNS servers you use to browse the internet. Here are the public DNS servers for you to use. You will not lose anything from your internet experience, however you gain so much more….make the change today, and free your internet.
Happy Browsing.
Due to a unforeseen issue, one of the public DNS servers was lost. However with reliable in mind, we have brought a new server online. This server is now operating at 100% and will continue to operate as long as UCANN2 gets funding…and by this I mean, I continue to earn money at a day job.
The new server is located in the Netherlands, so now the entire structure is spread across the earth.
For anyone polling our public DNS servers, please find the updated information below.
b.dns.ucann2 is 100% operational.
Below are the IP addresses of b.dns.ucann2.
199.193.250.116
2605:f700:80:800::73d9:863c
You can obtain the above IP addresses by doing
dig +short @a.ucann2.net b.dns.ucann2. a
dig +short @a.ucann2.net b.dns.ucann2 aaaa
DNS server a.dns.ucann2 is now operational and accepting DNS queries. See below the information to add a.dns.ucann2 to you resolver.
| a.dns.ucann2 |
|---|
| 192.157.220.140 |
| 192.157.220.251 |
| 2605:f700:40:c00::41c5:e40a |
| 2605:f700:40:c00::41ac:a4a8 |
I’ve started restructuring the UCANN2 infrastructure. New servers, MORE servers and a completely different naming convention.
This new infrastructure will allow beeter reliablty as well as faster resolver time. Since I’ve moved the DNS structure to a DLZ (Dynamic Loading Zone) setup, the updates are immediate.
So check back often for new servers coming online.
I’ve setup two more DNS servers :
92.222.21.155 -> Germany
5.135.167.84 -> France
How to make them available as root servers? should I add an entry to the “db.root” file?