The following domains are aliases using the same DNS data on the same servers, and all ultimately bringing you to this page:
The authoritative DNS servers for these domains are running the development branch of gdnsd, which fully implements DNSCurve in both Streamlined and TXT modes, over both UDP and TCP. A development snapshot (version 1.3.4) is now available for download here
In case anyone needs to quickly cut and paste while testing bits of code, the nameserver keys and IPs are:
uz5k71lf04u2h4xkvpktnz9lbt6p9v7l193zmsfnkkxb14574dl5mc
69.164.198.85
2001:470:1f0f:68a::1
uz5yv8kbbqykz940gbgtrtfztx0pnxl5dh83ycsfrbysvuh0pptpyd
69.164.220.36
2001:470:1f07:8b8::1
The official nameserver hostnames for the domains are the key above followed by the domainname itself, as would be normal for in-bailiwick DNSCurve authoritative servers.
These domains are also testing gdnsd's IPv6 DNS support as well, thanks to he.net's IPv6 tunnel services. All hosts and services here are v6-enabled, and gdnsd is serving proper forward and reverse (delegated from he) IPv6 data over IPv6 itself. I'm still sorting through getting AAAA glue added at my upstream registrars.
Within the test domains standard hostnames like "www" exist, as well as a wildcard "*.wild" which contains a few different RRs, for you to use for testing.
Direct access to the server instances' internal stats (normally, you probably wouldn't expose these in production) can be found here:
Aside from protocol testing, another important aspect of DNSCurve to test is that registrars and TLD servers don't balk at unusually long nameserver hostnames. Hence the multiple domain aliases: I wanted to test a few registrars and TLDs.
3 different registars were used: register.com, godaddy.com, and networksolutions.com. All of them accepted and published DNSCurve nameserver names correctly. In the overall, register.com was the easiest one to work with for someone who wants to manually configure custom nameserver hostnames and IPv4 glue.
On the IPv6 glue front: networksolutions.com has no direct interface for adding v6 glue, but they do have a note on their web UI to send email for manual v6 glue updates. I've sent that email, and should get a response by mid-next-week. register.com also has no direct v6 glue interface, and virtually no information available on the subject either electronically or via their first tier of tech support. I'm going to call them again monday and see if I can get better help. I have no conclusive info about godaddy.com. They appear to have some level of v6 glue support in their UI, but the only domain I have through them (dnscurv.es) is with a TLD that doesn't offer v6 glue yet (which their UI informed me of).
There's not much else to see here via HTTP, but feel free to explore the domain via DNS and test for interop (or other) bugs. Please direct any feedback to the gdnsd Google Group, the Issue Tracker hosted at Googlecode, and/or my personal email.