Jump to content

Talk:Reverse domain name notation

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Opening heading

[edit]

Examples

[edit]
  • Examples should be more generic.
maps.google.com -> com.google.maps etc. --86.134.154.148 (talk) 13:32, 8 January 2008 (UTC)[reply]
  • Is that still an issue? The current example of "com.example.MyProduct" seems pretty generic and descriptive. Suggest to remove/archive this if not needed anymore. --invenio tc 01:44, 6 March 2014 (UTC)[reply]

History

[edit]

The history section gives a false assumption, although technically true. Reverse-style DNS names are much more basic and have been around for much longer than Java. In the old days of computing, many addresses were in the style now called reverse, but I can't find a good reference right now. —Preceding unsigned comment added by 74.85.42.110 (talk) 18:24, 21 July 2008 (UTC) Ah, found my reference on FOLDOC: big-endian, definition 2 I guess it wasn't "many." Well, there were also bang paths... 74.85.42.110 (talk) 02:10, 6 December 2008 (UTC)[reply]

DBus

[edit]

DBus uses reverse-DNS, separating components with a slash instead of a period, as unique identifiers (I think for interfaces or objects). I think this is notable enough to be in the article.190.188.180.148 (talk) 22:42, 15 April 2009 (UTC)[reply]

Monotone

[edit]

Monotone also uses Reverse-DNS for unique branch names as explained in their manual[1].Yselkowitz (talk) 07:53, 23 December 2009 (UTC)[reply]

References

  1. ^ "Monotone documentation, section 1.7". {{cite web}}: Missing or empty |url= (help); Text "http://monotone.ca/docs/Branches.html#Branches" ignored (help)

Intro

[edit]
  • To me Reverse domain name notation is not the same as Reverse DNS as such, plus the article's name should be highlighted. I'm therefore suggesting to change the intro from

The Reverse-DNS is a naming convention for the components, packages, and types used…

to

The Reverse domain name notation is a naming convention for the components, packages, and types used…


Rename

[edit]
The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the move request was: page moved. Consensus was to expand the abbreviation. No consensus on what if any hyphens are needed. Vegaswikian (talk) 07:29, 28 November 2011 (UTC)[reply]


Reverse-DNSReverse domain name notation — Preceding unsigned comment added by 85.228.16.92 (talkcontribs) 01:15, 21 November 2011 (UTC)[reply]

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

"Rationale" section

[edit]

Is this article a stub? Readers coming here will certainly be looking for a description of the point of reverse-dns name notatation; right now it leaves them hanging. From the GNU mailing list link in the article, I gather that the purpose is to use the existing domain name ownership infrastructure to prevent name collisions rather than (insert the scheme in question here) having to deal with that themselves. However, I am just one of those readers. Paradox (talk) 05:11, 22 January 2015 (UTC)[reply]

I think I recall seeing a quote by Tim Berners-Lee that he regrets the current ordering of DNS labels, but I can't find it now. With Reverse-DNS notation, a URI becomes truly hierarchical: I think the intention was something like http://org/example/www/pages/index, with the idea that the whole thing is just a simple directory and you can serve up resources at any point. Each slash introduces a level below, rather than the current system where the TLD is in the middle of the URI. Darac Marjal (talk) 11:03, 2 October 2024 (UTC)[reply]

Remove "Code" section

[edit]

This article deals with the concept of reverse domain name notation rather than ways to reverse domain names. I suggest the "Code" section be removed. Magic sergeant (talk) 13:38, 7 July 2018 (UTC)[reply]

I agree it should be removed. Zoren.dk (talk) 10:54, 9 August 2019 (UTC)[reply]

Agreed, it is not relevant to the article. I will remove it. InverseHypercube (talk) 19:13, 2 December 2019 (UTC)[reply]

While listing code examples in lots of different languages might not be so relevant to the article, I still think it could be useful with either pseudocode or one code example in a easy-to-grasp language to illustrate the concept of how to programmatically reverse a domain name so it can be converted back and forth between its normal notation and reverse notation. -- Frap (talk) 17:55, 3 December 2019 (UTC)[reply]

Flatpak

[edit]

Flatpak uses reverse domain name notation as unique app identifiers as well. Ashrude (talk) 18:01, 15 September 2023 (UTC)[reply]

 Done Komonzia (talk) 00:29, 4 October 2024 (UTC)[reply]