4 ms·

Because that would break the internet. Third and lower level domains as they are known are resolved at the hosting server not in the DNS system.

ars 17y ago
I think you need to learn more about the DNS system. When you say lower I don't know which direction you mean, but it doesn't matter: there is no difference at all between any of the levels in DNS. None. They all get resolved in exactly the same way, just at different servers. Eg: www.en.google.com You start at the root sever and ask it about www.en.google.com and it says "I don't know, but I know that .com can be found at foo". You ask foo: and it says I don't know, but google.com can be found at bar. You ask bar and it says: I know this one, and it gives you the answer despite it being more than one level.
- dan_the_welder 17y ago
  Well perhaps I phrased it poorly. They get resolved in order as you explained, but en from en.google.com will only be resolved at Google's host DNS. I defacto own any weird combo of third, forth, etc order domains that live under my registered second level domain. So there is no way to do as you suggest in your original post with out substantially altering the DNS system by inserting one more layer into the public side. I could rent ars.danthewelder.com to you, but I don't think that's what you really meant in your original post.
  - ars 17y ago
    That isn't so. You don't have to change anything, you just add some more names for the root level servers to resolve. Everything will work just fine, with no changes at all on the client end, and no changes in the servers, except maybe you need a bit more hardware in the root servers. I told you - there is nothing at all special about any of the levels. danthewelder is just a name for the .com server to resolve, it could resolve any names, and .com is just a name for the root server to resolve - it could resolve any names. For example there is no reason at all you could not have email at ars@com - just com, with no other part to the name and http://com/ http://com/ could work just fine. There is no address set up for com, but there could be - those layers are not specially singled out.
    - dan_the_welder 17y ago
      You keep saying it's no big deal, but it is. I am the danthewelder server. Me personally, or my hosting service. You cannot resolve on my turf. http://itsmyturfand.youwouldbreaktheinterenet.danthewelder.com/ http://itsmyturfand.youwouldbreaktheinterenet.danthewelder.c...
      - ars 17y ago
        I had a whole reply typed up, but I removed it. I give up. You simply don't understand what I'm saying, and I can't keep trying.
        dan_the_welder 17y ago
        Well then you are not explaining it very well. If you sell person.slate.com to someone when slate.com is already sold to someone else, that means who ever owns slate.com cannot have their own person.slate.com subdomain. Tell me how DNS is gonna figure that out from a string of text URL? What you propose cannot be done with out taking something from the people who already own a particular domain.

ars 17y ago

I think you need to learn more about the DNS system. When you say lower I don't know which direction you mean, but it doesn't matter: there is no difference at all between any of the levels in DNS. None. They all get resolved in exactly the same way, just at different servers. Eg: www.en.google.com You start at the root sever and ask it about www.en.google.com and it says "I don't know, but I know that .com can be found at foo". You ask foo: and it says I don't know, but google.com can be found at bar. You ask bar and it says: I know this one, and it gives you the answer despite it being more than one level.

dan_the_welder 17y ago
Well perhaps I phrased it poorly. They get resolved in order as you explained, but en from en.google.com will only be resolved at Google's host DNS. I defacto own any weird combo of third, forth, etc order domains that live under my registered second level domain. So there is no way to do as you suggest in your original post with out substantially altering the DNS system by inserting one more layer into the public side. I could rent ars.danthewelder.com to you, but I don't think that's what you really meant in your original post.
- ars 17y ago
  That isn't so. You don't have to change anything, you just add some more names for the root level servers to resolve. Everything will work just fine, with no changes at all on the client end, and no changes in the servers, except maybe you need a bit more hardware in the root servers. I told you - there is nothing at all special about any of the levels. danthewelder is just a name for the .com server to resolve, it could resolve any names, and .com is just a name for the root server to resolve - it could resolve any names. For example there is no reason at all you could not have email at ars@com - just com, with no other part to the name and http://com/ http://com/ could work just fine. There is no address set up for com, but there could be - those layers are not specially singled out.
  - dan_the_welder 17y ago
    You keep saying it's no big deal, but it is. I am the danthewelder server. Me personally, or my hosting service. You cannot resolve on my turf. http://itsmyturfand.youwouldbreaktheinterenet.danthewelder.com/ http://itsmyturfand.youwouldbreaktheinterenet.danthewelder.c...
    - ars 17y ago
      I had a whole reply typed up, but I removed it. I give up. You simply don't understand what I'm saying, and I can't keep trying.
      - dan_the_welder 17y ago
        Well then you are not explaining it very well. If you sell person.slate.com to someone when slate.com is already sold to someone else, that means who ever owns slate.com cannot have their own person.slate.com subdomain. Tell me how DNS is gonna figure that out from a string of text URL? What you propose cannot be done with out taking something from the people who already own a particular domain.