rayhaanj

Oh that's anticlimactic, it was not obvious from that page, updated the title :)

Technically they’re used for the Cantons so to register a two letter CH subdomain you first need to register a new Swiss Canton!

Around 30 centiCHFs per KWh at the peak tariff: https://www.ewz.ch/en/private-customers/electricity/tariffs/...

I'm currently using joker.com after also migrating off of gandi.

I just did some measurements and am impressed on both fronts: DNS recursive resolution is faster than I anticipated, but also page load times for well optimised sites are also very fast (sub 0.5s). Here's some data:

Recursively resolve bbc.com: 18ms https://pastebin.com/d94f1Z7P Recursively resolve ethz.ch: 17ms https://pastebin.com/x6jSHgDn Recursively resolve admin.ch: 39ms: https://pastebin.com/DUTg8Rit

Page load in Firefox: bbc.com DOMContentLoaded: ~40ms, page loaded: ~300ms reuters.com DOMContentLoaded: ~200ms, page loaded: ~300ms google.com DOMContentLoaded: ~160ms, page loaded: ~290ms

So it's quite reasonable to do full recursive resolution, and you'll still benefit from caching after the first time it's loaded. One other idea I had but never looked into it was instead of throwing out entries after TTL expiry to just refresh it and keep it cached, no idea if BIND/Unbound can do that but you can probably build something with https://github.com/hickory-dns/hickory-dns to achieve that.

I think you mean "running your own recursive resolver", an authoritative server is one which is authoritative for some zone (e.g. example.net), whilst a recursive resolver is one that goes and walks from the root of the DNS hierarchy to the leaf that you have queried.

It is probably quite a bit slower though needing to have roundtrips at each stage of the resolution, which is also likely a reason that these public resolvers get so much use (latency improvement via caching).

You can download a list from here too: https://github.com/cisagov/dotgov-data/blob/main/current-ful...

> Users do not have to worry about security, SRF quotes Weber: "No data is transferred. There is only a link to the correct page."

Yes but how do you know you've resolved the right thing, it's still vulnerable to a compromise of another TLD.

I think you meant kilometres per second, not per hour.

Also 4_294_901_931 is actually just small enough to fit in a u32 whose max value is 4_294_967_295

There has been some work on encrypted server name indication: https://www.cloudflare.com/learning/ssl/what-is-encrypted-sn...

I've been working on a BGP implementation in Rust over the last few years: https://github.com/net-control-plane/bgp/

It's still in a proof of concept stage and nowhere as complete as GoBGP though.