...why?
My DNS server, my rules, no? Why should I feel obligated to follow ICANN? Obviously, I'll need to make changes if someone ever registers the domain with ICANN (and I want to access the ICANN version), but other than that...
...why?
My DNS server, my rules, no? Why should I feel obligated to follow ICANN? Obviously, I'll need to make changes if someone ever registers the domain with ICANN (and I want to access the ICANN version), but other than that...
The main issue is if it gets sold later, or assigned by RFC. As an example, more than one company I've worked for used .dev as a TLD for their dev environments, with local DNS to override it. Once google bought .dev, this meant that:
- we couldn't access anything Google put on .dev
- suddenly, all of our test sites had HTTPS forced, because .dev was HSTS preloaded by Google
The point here is that an unexpected change that you might not be aware is coming can break your setup in ways that are awkward to resolve - eg HSTS preloading means that you can no longer access non HTTPS endpoints unless you do it by IP and that leads to a frustrating afternoon - and it's inevitably always when you don't want it.
Like it or not, ICANN operates the DNS space. There's a proper way to get your own piece of this space, and you can run home or business networks under your own piece and you have a guarantee that no one will break you - because it's yours.
(edited for formatting)
That's harder than it sounds, with more and more apps implementing their own DNS over HTTPS clients - Firefox does it for instance, so does Chrome.
https://www.myhelpfulguides.com/2018/07/30/redirect-hard-cod...
Afaik nobody has a fix for the client hostility that DoH brings to the table.
Yes we have all abused unencrypted DNS to take the littlest bit of control back from hostile devices but we’re the minority of a minority who lose out in this situation where everyone else is now shielded from random sketchy Wi-Fi hotspots, and their ISP.
But a great counterargument would be "too bad, Firefox and now Google are doing it anyway, you lost and this is the world we live in, so deal with it." And, you'd have a point!
Not so important for you with your 200 tabs open, but quite important to the people maintaining the root servers who see a significant percentage of all queries being for bogus domains that don't exist.
I get the boys out rule sentiment, but isn't resolving domain names, even those that don't exist, the whole purpose of root servers?
I mean, your suggestion reads like asking not to type URLs wrong because a significant percentage of requests are 404s.
The root servers shouldn't be a dumping ground for unnecessary traffic when proper DNS configuration is not that difficult.
No DNS hardware is smart enough to know that you meant ".arpa" not ".apra" you actually typed in.
Typos are not really a valid argument, it can happen for any type of domain.
That's what a former employer had set up for their internal environments.
Worked great until mDNS came along and Apple devices insisted that .local had to go through mDNS rather than our DNS servers.
The Mac users had a constant stream of complaints because of it: "I can't connect to the printer", "Shared drives don't work", "I can't access the CI environment in Safari/Chrome/whatever"
Also, does your DNS server correctly filter "out"-of-bailiwick responses for .lan etc. zones that are actually perfectly well in-bailiwick because they're from the actual delegated-by-the-real-root-servers nameservers, they're just not from your private server that you've configured? If not, I can execute a cache-poisoning attack against you.
I use `.zz`.
It's short, easy to type, and in order for that to be assigned out, we'd need an entirely new country to be created (one that decided the other bazillion free CCTLDs are not to their liking). And like you say, I only run into a problem if I decide I want to access things from said country.
Would I do this in any professional setting? Absolutely not. For my own stuff at home? The risk is pretty minimal and the work involved in updating if I ever have to is not too bad.
DHCP automatically registers everything under <hostname>.zz, and I cname well-known things from <thing>.svc.zz to the appropriate hostname so I can hit, e.g., `blueiris.svc.zz` or `homeassistant.svc.zz`.
For SSL I just run my own CA.
https://tools.ietf.org/id/draft-ietf-dnsop-private-use-tld-0...
> are thought to be plausible choices for the implementation of private namespaces
[ISO3166 clause 8.1.3] "User assigned code element":
"If users need code elements to represent country names not included in this part of ISO 3166, the series of letters AA, QM to QZ, XA to XZ, and ZZ, and the series AAA to AAZ, QMA to QZZ, XAA to XZZ, and ZZA to ZZZ respectively and the series of numbers 900 to 999 are available."
This is not the argument you think that it is.
> zz is safe for personal use. Those guidelines will not change
Right. Safe for personal use within the range of uses for ISO 3166—guaranteed not to collide with any future two-letter country code. It's not a commitment from ICANN, which remains free to say, "ISO 3166 guarantees no collisions for AA. We choose, therefore, to open up bidding to auction off aa, which is expected to fetch a pretty penny as the first of a limited set of possible TLDs that are < 3 characters long."
That's the same line taken by network admins who think they know better than using RFC1918 IP ranges for their LAN.
As a satellite office and an acquisition, we played all kinds of games to try to figure out whether we should send a given IP address out to the Internet or to corporate. Apple’s IP range was entirely overlapping and of course the corporate networking group just threw up their hands and said “send it to us; the internet is not a business critical function.”
This was in the early 2000s, not the early 90s.
To pick your own free TLD just run a nameserver check against the TLD on [1] and watch out for TLDs that hit root servers
But you seem to be on our network with all of us and so here you need to obey our rules or things won't go so well for you.
Sounds like a toothless threat.