9 ms·
Special-Use Domain 'home.arpa.'
- jawns 8y agoJust in case you're wondering, as I was ... https://en.wikipedia.org/wiki/.arpa https://en.wikipedia.org/wiki/.arpa > While the name was originally the acronym for the Advanced Research Projects Agency (ARPA), the funding organization in the United States that developed one of the precursors of the Internet (ARPANET), it now stands for Address and Routing Parameter Area.
- ktpsns 8y agoThat's a brilliant trick to depoliticise an essential part of the DNS.
- Waterluvian 8y agoIn my town Waterloo Lutheran University became Wilfrid Laurier University. I thoroughly enjoy backronyms.
- gowld 8y agoNot a backroynym, but King County, Washington retroactively changed which person named "King" is its namesake.
- empyrical 8y agoThere was a school called "J. Edgar Hoover School", which changed so it was named after Herbert Hoover http://articles.chicagotribune.com/1994-06-26/news/9406260229_1_pta-honored-president http://articles.chicagotribune.com/1994-06-26/news/940626022...
- gowld 8y agoShame that that article puts "cross-dressing" on par with "wire-tapping, Constitution-stomping, blackmailing, bully". We've come a long way, and still have a long way to go.
- xori 8y agoThat's a shame, I liked the previous .home
- Spivak 8y agoThere's a good chance that .home will be reserved forever simply because it and a lot of other names have widespread internal use. https://tools.ietf.org/id/draft-chapin-rfc2606bis-00.html https://tools.ietf.org/id/draft-chapin-rfc2606bis-00.html
- deleted 8y ago[deleted]
- reaperducer 8y agoI still sometimes see .arpa in my server logs. I don't know if it's a spoof, or a misconfiguration, or just cruft, but it's there. (I still miss Australia being .oz, instead of .au.)
- adw 8y agoin-addr.arpa is the reverse zone.
- zAy0LfpBZLC8mAC 8y agoThat's the legacy reverse zone, the state of the art reverse zone is ip6.arpa.
- twic 8y agoIncredibly, .gb lingers on: $ getent hosts hermes.dra.hmg.gb 146.80.9.16 hermes.dra.hmg.gb
- reaperducer 8y agoI think .su is still a thing, but not being assigned anymore.
- walrus01 8y agoreverse DNS for everything in public IP space uses the in-addr.arpa extension. https://www.google.com/search?client=ubuntu&channel=fs&q=reverse+dns+in-addr.arpa&ie=utf-8&oe=utf-8 https://www.google.com/search?client=ubuntu&channel=fs&q=rev...
- tinus_hn 8y agoIn other words, they got a lot of money and then they sold the .home tld.
- cpburns2009 8y agoI think it has more to do with this: > There is an existing process for allocating names under '.arpa.' [RFC3172]. No such process is available for requesting a similar delegation in the root at the request of the IETF, which does not administer that zone.
- NSAID 8y agoNot the case. > In response to the report, ICANN labeled the .home and .corp strings as "high risk" and proposed that neither of the strings be delegated until it could be proven that risk is low. These two strings are currently severely delayed and some community members guess they may never be delegated. https://icannwiki.org/.home https://icannwiki.org/.home
- BuildTheRobots 8y agoI'm always surprised .internal never took off. x.home.arpa doesn't quite sound right for the office lan.
- da_chicken 8y agoSo am I reading that right? A significant number of people are using .home and .corp as the TLD for their local or internal network domains, so ICANN decided to (possibly indefinitely) delay delegation of those TLDs?
- wyldfire 8y agoI've seen .local and .lan DNS suffixes and assumed that they were specified in a standard somewhere. Perhaps not.
- cpburns2009 8y agoI don't think they're standard. The RFC references "Special-Use Domain Names" [1] which contains a list of special use domains. I'm confused about ".local" though. It's reserved for Multicast DNS? [2] [1]: https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml https://www.iana.org/assignments/special-use-domain-names/sp... [2]: https://tools.ietf.org/html/rfc6762#page-67 https://tools.ietf.org/html/rfc6762#page-67
- sigjuice 8y agoMulticast DNS is the special use.
- djsumdog 8y ago.local has always been confusing
- sigjuice 8y agoResolving a .local domain name works like this. $ dig -p 5353 raspberrypi.local @224.0.0.251 ; <<>> DiG 9.8.3-P1 <<>> -p 5353 raspberrypi.local @224.0.0.251 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21640 ;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;raspberrypi.local. IN A ;; ANSWER SECTION: raspberrypi.local. 10 IN A 192.168.1.175 A DNS query packet is to the multicast address 224.0.0.251 and UDP port 5353. All devices on your network that are listening on that address will see the query (e.g. Linux systems with avahi-daemon or Macs running mDNSResponder). The device whose name is raspberryi will respond. RFC6762 should have all the details.
- 8_hours_ago 8y ago
- LeoPanthera 8y agoSo, my home LAN does indeed use .home. Is this going to fuck that up?
- organsnyder 8y agoNope. This merely specifies that home.arpa is reserved for uses such as yours. It would probably be a good idea to switch to using home.arpa in case .home is ever allocated in the future, though that doesn't seem likely right now.
- tdy721 8y agoYou have been spied upon. Our bad, we will ignore legit citizens at home.arpa
- zokier 8y agoNo, this RFC is not going to fuck that up. But some other might. Hijacking random domains is not a great idea, especially when domains cost only few bucks.
- paulddraper 8y agoWait...are you suggesting going to a domain registrar when I want to give my printer a hostname?
- wrigby 8y agoWell... maybe. You would just register the domain once (maybe `mycoolawesomehome.net`), and then you have the authority to arbitrarily decide that your printer's hostname should be `thebestprinterever.mycoolawesomehome.net`. But now you can just use `mycoolawesome.home.arpa` without registering it.
- gerdesj 8y agoIf you are the family IT bod you could register familyname.co.tld (.uk for me) or .org.uk or whatever. Then allocate each family branch their own subdomain. In the UK you are looking at around £20 per year for a .co.uk and not much more from say 1-2-3 for hosting/DNS. Now you can get Lets Encrypt certs for routers and all sorts! Use a Dynamic DNS service if external IPs are not static. My family may be a little unusual in that even my Dad's TV has a hostname, and so has my brother's cooker! I put in pfSense, multiple VLANs, Unifi APs and all the other good stuff. A fully meshed IPSEC VPN link up with split horizon DNS. pfSense has an ACME client and a full toybox of networking goodness. Each site config is mostly replicated to the others for backup. The office monitoring system (Icinga) has a few extra systems on it. That lot took a couple of man days to set up. It looks after itself mostly now and just works. I've saved myself many, many hours of hassle by putting in the work ahead of time and specifying decent gear. Its probably not for everyone.
- staunch 8y agoThis is good for small stuff but most people should just register their own domain name. It's so cheap now and such a benefit to have a publicly-accessible and publicly-reserved address. There's no need to make your DNS records publicly-accessible although it's often convenient and rarely a risk.
- djrogers 8y agoThis is for residential networks - that is by definition small stuff. Registering a domain and running DNS is overkill for most residential networks, and well beyond the skill level and time commitment warranted for home use.
- deleted 8y ago[deleted]
- forapurpose 8y agoIn case this issue on pages 7-8 is overlooked: Because 'home.arpa.' is not globally scoped and cannot be secured using DNSSEC based on the root domain's trust anchor, there is no way to tell, using a standard DNS query, in which homenet scope an answer belongs. Consequently, users may experience surprising results with such names when roaming to different homenets. To prevent this from happening, it could be useful for the resolver on the host to securely differentiate between different homenets and between identical names on different homenets. However, a mechanism for doing this has not yet been standardized and doing so is out of scope for this document. It is expected that this will be explored in future work.
- phicoh 8y agoIn case people wonder why .home was not picked. One of the many issues here is that the current policy for the root DNS zone is that all new delegations from the root zone have to support DNSSEC. So they have to have DS records. Given that the IETF specifically needed to "home" zone to be unsigned, that would result in lengthy process to change the policy for the root zone. The root zone is managed by ICANN who implement the IANA function. And then operationally managed by Verisign. In the end using something under .arpa, solved a lot of issues. It is quite possible that the IETF could have allocated .home because it is currently unused. But that would still require solving the technical issues. At the same time, as long as there is wide spread use of .home, ICANN cannot really allocate that as a new gTLD. So it should be sort of safe to continue to use that. But "homenet" compliant routers should come with home.arpa preconfigured.
- forapurpose 8y agoWhy not just reserve .home permanently so that it won't be allocated and tell people to use it? Does that somehow result in more bogus traffic to root and other DNS servers? Between the lines, I read that ICANN doesn't give a f- about home users. Home users are not on the ICANN board (they've never heard of ICANN), don't give presentations at conferences or write papers, don't talk shop over lunch with ICANN members ... home users are invisible and have no voice. 'So here's this kludge that requires zero effort from us, is probably a little confusing for you[0] - we hope you like it because we're not doing anything more.'