User Controls
I know it's basic
-
2019-03-07 at 8:44 PM UTCWhat's the purpose of having a . in a domain name?
For instance...
kr0z.com
bill.kr0z.com
kr0z.bill.com
bill.kr0z.by.com
kro0z.bill.by.com
What's the difference? What does it mean?
Also, what is with 'www2'?...
www2.kr0z.com
www.kr0z.com
Are they the same? Is the 'www' even needed? -
2019-03-08 at 2:47 AM UTCIn the example www.google.com:
www is the hostname.
google is the domain name.
com is the top-level domain name.
You can have all kinds of variations on this same pattern, but ultimately it comes down to a SINGLE domain name registered to a SINGLE top-level domain name (usually denoting country of origin, or .net, .org, .edu, or even novelty ones like .space or .sex).
The initial hostname portion can vary quite a bit.
You can stick to the standard www, or you can have, say, mail.google.com, or books.google.com, etc.
Or you can even leave it out altogether (as you see in niggasin.space).The following users say it would be alright if the author of this post didn't die in a fire! -
2019-03-08 at 3:21 AM UTCBut wait about the dot??? You didn’t answer the OP’s most important question!
-
2019-03-08 at 3:26 AM UTCHttpsniggasinspacethread35046
-
2019-03-08 at 3:41 AM UTCIt doesn't really matter what you name it, as long as it translates to a number. The domain is just the label. Even the number is just a label. It's just a way people can communicate and understand each other. The domain name, or its format, even the dot, is not even really required by the machine, as long as it has the number. The name is merely to make it user-friendly, nothing more.
-
2019-03-08 at 4:27 AM UTCOkay, it's analogy time...
Say you have a physical address as follows:
1600 Pennsylvania Ave NW
Washington, DC, USA
In order to route someone to that particular address, you first start with the "top-level domain" (in this case, "USA").
To sustain the DNS metaphor, we'll consider wa.dc.usa to be series of top-level domain identifiers.
Now, the actual building's physical address is analogous to the domain name.
So let's call it 1600-pennsylvania-ave-nw.wa.dc.usa.
But what if you want to rent out a room in the White House (lol)...
Then they might get their own suite called Apartment B.
So you could then start dividing that domain up into multiple hosts...
http://ovaloffice.1600-pennsylvania-ave-nw.wa.dc.usa for official presidential matters.
http://apartmentb.1600-pennsylvania-ave-nw.wa.dc.usa for the skater bum renting a room to blog about skate parks and whatnot.
Does that help at all?
I just did a few bumps of ketamine and I might be WAAAAAYYYYYY off on a tangent. -
2019-03-08 at 4:29 AM UTCBut why does it have to have a dot to separate each part
-
2019-03-08 at 4:30 AM UTCWhy couldn’t it be a comma or some shit
-
2019-03-08 at 4:31 AM UTC
Originally posted by Methuselah But why does it have to have a dot to separate each part
That's just a convention.
They could have used exclamation marks or question marks or freaking emojis if they wanted to.
You need some kind of symbol to instruct the browser and DNS services how to parse a particular URL. -
2019-03-08 at 4:32 AM UTC
-
2019-03-08 at 4:32 AM UTCOk well then I think that’s all the questions answered. Thank you gadzooks for breaking your hiatus/sabbatical or whatever the fuck to come answer our readers’ burning questions!
-
2019-03-08 at 4:34 AM UTC
Originally posted by Methuselah Ok well then I think that’s all the questions answered. Thank you gadzooks for breaking your hiatus/sabbatical or whatever the fuck to come answer our readers’ burning questions!
It's a quasi-hiatus. I pop in from time to time.
I've started paying especial attention to this subforum though because I like talking just about anything computer science or programming related. -
2019-03-08 at 4:37 AM UTC
Originally posted by Methuselah Why couldn’t it be a comma or some shit
Usually this type of thing simply comes down to whatever was posited (and implemented) first.
Now, if we wanna have some real fun with URL parsing, we could get into Base64 encoding, HTTP request types and their respective parameter encoding, cookies, sessions, SSL/TSL handshakes, alternative protocols to HTTP(S), etc, etc, etc. -
2019-03-08 at 9:10 AM UTCFor, lets say, www.totse.com the thought process went something like this.
.com would be the DNS computer.
totse would be the company registered with that DNS computer.
www. would be a computer at the company - like the computer that served http.
Dots were chosen I guess as they were used in the decimal system in most countries, for instance $10.00 -
2019-03-08 at 2:26 PM UTC
-
2019-03-08 at 2:45 PM UTCNow my brain hurts reading this thread.
-
2019-03-08 at 3:31 PM UTC
-
2019-03-08 at 8:32 PM UTCSo is the 'www' necessary?
Is it just for looks? -
2019-03-08 at 8:57 PM UTC
Originally posted by Admin So is the 'www' necessary?
Is it just for looks?
Its not strictly necessary, but it does serve a purpose.
E.g. If you want to distinguish between the search engine (www.google.com) and the Google mail (mail.google.com).
But www is just the default host for any given domain, so you dont have to actually refer to it. -
2019-03-08 at 11:05 PM UTC
Originally posted by MORALLY SUPERIOR BEING V: A Cat-Girl/Boy Under Every Bed .com would be the DNS computer.
For the sake of understanding this is reasonable, but it's not like different TLDs have different DNS servers or anything. Any general purpose DNS server will service lookups on any TLD and the authority that assigns domains is different than those that run DNS servers.
Originally posted by Admin So is the 'www' necessary?
Is it just for looks?
DNS predates HTTP, when early web servers were being set up it was common to put web servers on a different machine and point the www subdomain to it. Since these days most people buy domains primarily to host an HTTP server on them, it's become more and more common to drop the www part since it's the main service on the domain. Some places still do the www thing just for legacy purposes but I would be 100% fine if the convention just died tomorrow.
