6 ms·
Is it not recommended for the Part C to be done with a third, yet publicly owned, domain? Instead of widgets.local or widgets.internal, it would be widgets-inte
by unethical_ban 8y ago
Is it not recommended for the Part C to be done with a third, yet publicly owned, domain? Instead of widgets.local or widgets.internal, it would be widgets-internal.com or something.
Struggling to remember why, but I heard people mad about .local
- mjevans 8y agoIt USED to be that .local was fine; no one else and no other standard used it. That changed; this is what people are / were mad about. The point is that some standard CAN change any other similar thing at any point in the future; particularly now that you can buy a TLD. Thus the lesson is, buy a real name and reserve the namespace.
- y4mi 8y agothe gTLD local is already registered and can't be 'stolen'. DNS servers should never route a query for that domain. you even get a link to the RFC when installing kubernetes with the default domain name (which is local). I sadly forgot the number, so cant cite it.
- y4mi 8y agothis should be the rfc: https://tools.ietf.org/html/rfc6762 https://tools.ietf.org/html/rfc6762 from wikipedia: > The Internet Engineering Task Force (IETF) standards-track RFC 6762 (February 20, 2013) reserves the use of the domain name label local as a pseudo-top-level domain for hostnames in local area networks that can be resolved via the Multicast DNS name resolution protocol.[1] Any DNS query for a name ending with the label local must be sent to the mDNS IPv4 link-local multicast address 224.0.0.251, or its IPv6 equivalent FF02::FB. Domain name ending in local, may be resolved concurrently via other mechanisms, e.g., unicast DNS.
- mjevans 8y agoThere are two interwoven threads of logic in my post. You've mistaken the second as limited to the first when it is building upon it. To clarify: It /used/ to be that .local wasn't mentioned in any standard. Don't do anything like .local (a non TLD and not part of a standard), because there is now a history of standards being created that break existing private deployments, and also because OTHER TLD like things can now be purchased as TLDs. That is why the current best practice is now to have an internal subdomain of a real domain (even if not globally published).
- walrus01 8y agomaybe .local was not the best example. In my opinion it's recommended to do with something that's not a public domain at all, since your DNS is entirely internal, you can set up bind9 servers to be authoritative for the root. You could have it by anything totally arbitrary of your choice for a top level domain, that is a non valid public domain or TLD, like widgets.burrito
- forapurpose 8y ago> In my opinion it's recommended to do with something that's not a public domain at all ... The recommended practice, AFAIK, is to register a public domain for the purpose. See the recent HN discussion of .home.arpa for all the reasoning and arguments and counter-counter-counter-points.
- walrus01 8y agoReally large ISPs have even planned for the disaster-recovery scenario of a collapse of public DNS infrastructure, so their internal management network and hostnames are not related to the existing gTLD or ccTLD, or legacy TLD in any way. There is no need to involve ICANN-approved TLDs in your internal DNS infrastructure, particularly if you have management interfaces for a lot of things that are firewalled off or air gapped from ever touching the public internet.
- kiallmacinnes 8y agoWhat does ICANN have anything to do with this? If the global DNS system crashed and burned, you would be in exactly the same place as if you had invented a TLD as you have suggested. But, if that doesn't happen... And the way more likely outcome of your "made up TLD" becoming real happens instead, you're in a way worse position. So far I've read you suggest .taco, .burrito, and .burritocorp as good TLDs to pick. This is terrible advice. Purchase a public domain name from a real TLD - use it knowing it's yours, and never going to conflict.
- walrus01 8y ago
- Sylamore 8y ago.local implies multi-cast DNS, you can't get a signed certificate for .local from any major certificate vendor either. See: http://www.mdmarra.com/2012/11/why-you-shouldnt-use-local-in-your.html http://www.mdmarra.com/2012/11/why-you-shouldnt-use-local-in...
- walrus01 8y agoTo avoid stupid software breakage you should never use .local for anything. Choose any other TLD for internal use, doesn't matter what it is, as long as it isn't a real TLD that exists in the new gTLD and ccTLD system. On a large scale for all internal stuff you are going to have your own, internal root and intermediate CA. The root CA signs the intermediate CA, the intermediate CA then signs SSL/TLS certificates for your internal infrastructure things. As an example for a mid sized ISP with such a setup, the internal ticket portal for the NOC is accessible only while physically in the office or when on the VPN, speaks TLS1.2 only to standard web browser clients, and its URL is https://portal.tickets.burrito https://portal.tickets.burrito where the "burrito" is obviously not the real name, I've changed it for this example, but the choice of TLD in your own internal DNS infrastructure is totally arbitrary. Then the individual clients all have the public certs for the internal corporate root and intermediate CA installed in them, so that they trust certificates signed by the internal CA. If you're big enough to care about having a serious multi-state-scale intranet, you probably don't want to be reliant upon external CAs to sign your stuff. Having your own internal CAs lets you do a lot of other things as well, without additional cost, such as sign per-client-device certificates as well.
- enzanki_ars 8y agoPlease do not suggest people use TLDs that are not a part of the gTLD, ccTLD, sTLD, or any other TLD system. Just because they are not used now does not mean they will never be used. We just saw the effects of that with 1.1.1.1 DNS system, where people assumed it would never be used, and when it does, now things break. Currently, the only reserved TLDs are: - [RFC 6761] example - [RFC 6761] invalid - [RFC 6761] localhost - [RFC 6761] test - [RFC 6762] local - [RFC 7686] onion With the exception of localhost, local, and onion, these can be used without any worry about future use. Any others should be considered real TLDs and not be used unless you actually own the domain name under that TLD. [RFC 6761]: https://tools.ietf.org/html/rfc6761 https://tools.ietf.org/html/rfc6761 [RFC 6762]: https://tools.ietf.org/html/rfc6762 https://tools.ietf.org/html/rfc6762 [RFC 7686]: https://tools.ietf.org/html/rfc7686 https://tools.ietf.org/html/rfc7686
- reaperducer 8y agoAnd .dev. Nothing is really safe. Maybe an emoticon? IIRC, the use of emoticons was stopped after someone registered the poop symbol on .la.
- walrus01 8y agofrom a dns server zonefile perspective, it's still plaintext, just some unicode string with the xn-- prefix on it... https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Internationalized_domain_name https://panic.com/blog/the-worlds-first-emoji-domain/ https://panic.com/blog/the-worlds-first-emoji-domain/ http://xn--ls8h.la/ http://xn--ls8h.la/ unicode 1f32e is the taco emoji, so i think I will be migrating all my internal things to http://servername.1f32e http://servername.1f32e
- pointytrees 8y agoWhat's worse about dev is that chrome auto-forwarded to the https version even if you were using it internally for testing using your hosts file.
- synotna 8y agoThat is the hsts preload list, used across bruises; .dev is no different than any other domain on the list, only that it was the first tld
- deleted 8y ago[deleted]
- dfox 8y agoSomewhat common pattern for (C) is using names like foosrv45.hide.example.com if you don't want to register another domain for that purposes. For convenience of the DevOps team it even makes sense for such hostnames to be publicly resolvable (to your internal IPs). One issue with doing this is that it tends to break in various wonderful ways when you internally use Windows and Active Directory.
- walrus01 8y agoFor various security reasons it's a bad idea for your internal hostnames to be publicly resolvable from anywhere on the internet, unless you're on a VPN, and therefore possible for your client device stub resolver to query the internal DNS server that only talks to internal IP space. Even if the internal hostnames only resolve to a non-globally-routable IP address somewhere in 10/8 or 172.16/12, etc.
- dfox 8y agoIn my opinion the convenience gained is more significant than these mostly theoretical "various security reasons". In other words when exposing hostnames and addresses of your internal infrastructure to the public internet has meaningful security ramifications then you have considerably more critical security problem.
- walrus01 8y agoIf you already have a proper, working VPN solution for remote access into the internal IP space, which any ISP will already have for network engineer staff and noc purposes... What great convenience do you gain by making the DNS and internal IP space scheme public?
- pdkl95 8y agoWho said anything about making IP addresses public? You seem to be assuming registering a domain name implies delegating that domain to an actual name server that must respond to public requests. These assumptions are both incorrect. Registering a domain prevents those names from being used for other purposes in the future. Your domain does not have to have valid NS addresses. Even if a domain has NS record with a valid address of the authoritative name server, that server does not have to respond to requests from the public internet. It doesn't even have to have to be accessible on the public internet. Register a domain for internal use and run an internal name server on e.g. 10.x.y.z that handles your private IP space, and configure the local recursive resolver name servers to hand out your internal server's address when asked about the associated NS record. At the same time, set the real NS records for your internal domain to e.g. a traditional DNS hosting service that returns a CNAME pointing to your public domain. (the public internet only sees *.private.example.com as a CNAME to www-public-name-com.example.com)