I did smile when I saw it was by DNSimple, absolutely love using them.
EDIT: I'm not a shill for these guys, but I signed up with them very early on and their customer service was fantastic. What made me become a (hopefully) life-long customer was when I emailed them to say that as a result of a botched cochlear implant surgery leaving me very sick, and out of work I could no longer pay my plan -- and they actually offered to help pay all my services I had with them until I was back on my feet! It was a small token on their behalf but so appreciated by me (but I asked a friend to meet the repayments instead to try maintain some self dignity). I just thought I should share this wee story!
The PSL has a quite different meaning, this list is enhanced with a lot of suffixes that are not actually TLDs. You may want to refer to https://github.com/weppos/ianawhois instead.
DISCLAIMER: I'm both a maintainer of the Mozilla PSL and the linked GitHub repo.
Yep, this is another tool we built to help troubleshoot zone issues. We also use it to provide data for some parts of the DNSimple UI since zone.vision has an underlying API (http://api.zone.vision/)
So, according to this the .COM TLD server, when asked to resolve dnsimple.com, would say 'ask ns1.dnsimple.com'? That still requires resolving dnsimple.com, which seems circular. Surely the .COM TLD server would give the IP address of the authoritative name servers for the domain?
ICANN doesn't really control TLDs either. All ICANN does is grant monopolies. Once the monopoly is granted they do very little. You could argue they're a regulator, but they have close to zero enforcement power.
Agreed, I would imagine for someone who doesn't know about glue records, the "road trip to ns1.dnsimple.com" must be super confusing since it doesn't explain how to find their location.
Ah, I'll confirm that imagining. I'm unfamiliar with glue records. How I've not encountered them I don't know, and it should possibly concern me. Maybe I have and have forgotten. Anyway, I was thinking hang on, back to square one, where do we get the ns ip addresses, we're going to go round in circles. Thanks for filling in the missing piece.
Beside the hundreds of new nonsense TLDs you have domains being taken down for copyright infringment or dissident suppression, name squatting and of course domain name frontrunning by registrars
And then there are of course DNS aimed DDOS attacks etc
Something needs to be done (yes I heard of namecoin) since the web as we know it is getting shittier by the year :(
Front running is more or less fixed by naming and shaming the registrars. I'll start:
GoDaddy is well known for domain name frontrunning. If you search for the availability of a domain using their website, they will likely temporarily register that name, forcing you to use them as a registrar. Use an alternative like gandi.net or Google Domains.
> ...then there are of course DNS aimed DDOS attacks...
Traffic amplification attacks are possible with protocols that return more data than one sends to trigger the return.
> Something needs to be done...
Do you, yc1010 have either a specific list of problems with DNS-the-protocol and/or DNS-the-distributed-name-to-address-mapping-system or a set of proposed solutions? :)
I did smile when I saw it was by DNSimple, absolutely love using them.
EDIT: I'm not a shill for these guys, but I signed up with them very early on and their customer service was fantastic. What made me become a (hopefully) life-long customer was when I emailed them to say that as a result of a botched cochlear implant surgery leaving me very sick, and out of work I could no longer pay my plan -- and they actually offered to help pay all my services I had with them until I was back on my feet! It was a small token on their behalf but so appreciated by me (but I asked a friend to meet the repayments instead to try maintain some self dignity). I just thought I should share this wee story!