31–40 of 174 posts
Earlier quoted context omitted.
somedomain.com is not guaranteed not to interfere! example.com is guaranteed not to interfere (and example.org) http://www.iana.org/domains/reserved
I believe you took their post too literally; they mean to go register some domain you would like to have (such as ilovemycoolhouse.com or bearinabigblue.house) and use it, because the only way it will ever interfere with something is if you cause it to.
The blog post misses the (controversial if you're one of the ex-applicants) decision by ICANN to ban .corp, .home and .mail from ever appearing on the internet. So you've got those options too. Or in ICANN management-speak: "Whereas, the Board considered that the applicants were not aware before the application window that the strings .CORP, .HOME, and .MAIL would be identified as high-risk, and that the delegations…
> Do not use undelegated domain names like .lan, .home, .homenet, .network, nor should you make up your own domain name. ...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...
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"
Earlier quoted context omitted.
I believe you took their post too literally; they mean to go register some domain you would like to have (such as ilovemycoolhouse.com or bearinabigblue.house) and use it, because the only way it will ever interfere with something is if you cause it to.
I hope you never forget to renew that registration...
> Do not use undelegated domain names like .lan, .home, .homenet, .network, nor should you make up your own domain name. ...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...
For what it's worth, this does work. For now. 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 Goog…
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.
Earlier quoted context omitted.
The issue here being: what happens when you have your proxy configured as "proxy.lan" but you make a typo when entering it in local DNS or in your browser settings? That DNS request for "proxy.lan" will now go all the way out to the root servers for every page load, multiple times. Not so important for you with your 200 tabs open, but quite important to the people maintaining the root servers who see a significant pe…
> (...) 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.
I just use a real domain name, so I can easily obtain LE certs. Only the internal DNS server will actually return internal addresses.
However, running split-horizon DNS is not straightforward, at least in a home setting. I don't see a huge problem with putting a couple of internal addresses in external DNS servers.
lexicon cloudflare --auth-token $(gopass cloudflare) create my-real-domain.xyz A --name my-rpi --content 192.168.1.201What about .localhost? Asking for a friend.
What about .localhost? Asking for a friend.
Heh. I starred this Android feature request and kind of regret it because it's been a continuous stream of "+1" emails (but I want to stay subscribed in case some meaningful conversation happens at last):
https://issuetracker.google.com/issues/140786115
(A login is required; any Google account will do)