follow the link -
http://no-www.org/

how to register such domain ?

Register such a domain as what??

Originally Posted by chrishirst

Register such a domain as what??

He wants to know how to register a no-www. domain.

But that would be a rather pointless question, as EVERY hostname registered is "without" www.

Yeah , as Chris has said..

Domains are registered like: domain.com

You simply add the WWW as a DNS record for the domain afterwards.

yes, I know domains are registered as domainname.x but when we enter address like domainname.x it appears to be www.domainname.x in address bar.
so is it simply rewrite rule with htaccess or something else?

Nothing to with .htaccess, which is a configuration file for an Apache webserver.

www is a subdomain that is added to the Domain Name System (DNS) server records as an 'A' record (IP Address) or a CNAME (Canonical Name) which is an ALIAS to a 'A' record.

The use of the 'www' sub domain as the primary site address has simply become commonplace from the early days of the World Wide Web.

why did people start to use the www. in the first place?

//******* edit ********//

i googled around for a while and found an article with a logical reason

The only remotely sensible reason I came across is that back in the early days of the world wide web, it was used to distinguish the web site of a domain from the FTP server or mail server (which would be ftp.example.com and mail.example.com, etc). So it seems to be nothing more than a convention that caught on.

Any domain can be used without the www.
I type my domain into the address bar without the www all the time.

Originally Posted by cantletugo

Any domain can be used without the www.
I type my domain into the address bar without the www all the time.

not true. try visiting www.thetrainline.co.uk/ and then try visiting it without the www.

Originally Posted by Peter1paket

Using WWW isn't necessary nowadays.

And never was!

Originally Posted by chrishirst

And never was!

Actually Chris, the quote under this came to my attention. Maybe you understand this better than I do, but flexdesigns has brought up a point I have no explanation for.

Originally Posted by flexdesigns

not true. try visiting www.thetrainline.co.uk/ and then try visiting it without the www.

I don't believe it's an .htaccess issue, it didn't connect to the server when you took away the "www." this is something I haven't the slightest clue as to what's going on.

I'll assume you know what the Domain Naming System (DNS) is though not necessarily how it works, not that you actually need to. Suffice to say it is the Internet quivalent of a telephone directory, where you can lookup a name and it will tell you the number to dial. In DNS parlance this is an 'A' record
Now, keeping that analogy, several people (a family) may reside at that property or in the case of a company, departments, so our system needs to be able to differentiate between those people or departments. In the case of a telephone call you would ask for the person, with HTTP requests you don't ask instead a name is prepended to the location such as ftp, mail, booking or www.

The reason for the hostname and the 'www' being one and the same is purely historical and simply comes from Tim Berners-Lee naming his invention being called the World Wide Web.

Originally Posted by chrishirst

I'll assume you know what the Domain Naming System (DNS) is though not necessarily how it works, not that you actually need to. Suffice to say it is the Internet quivalent of a telephone directory, where you can lookup a name and it will tell you the number to dial. In DNS parlance this is an 'A' record
Now, keeping that analogy, several people (a family) may reside at that property or in the case of a company, departments, so our system needs to be able to differentiate between those people or departments. In the case of a telephone call you would ask for the person, with HTTP requests you don't ask instead a name is prepended to the location such as ftp, mail, booking or www.

The reason for the hostname and the 'www' being one and the same is purely historical and simply comes from Tim Berners-Lee naming his invention being called the World Wide Web.

This is definitely something I am unfamiliar with, yet I am still confused as to why that site above reacts differently with or without the 'www" because of this:

Originally Posted by chrishirst

The reason for the hostname and the 'www' being one and the same is purely historical and simply comes from Tim Berners-Lee naming his invention being called the World Wide Web.

There is a practical reason for differentiating between www.domain.com and domain.com.

http://tycoontalk.freelancer.com/dom...ml#post1101577

Originally Posted by NullPointer

One reason it is still used has to do with cookies. Standards dictate that a cookie set for a domain (ie example.com) should be included in any request made to both that domain, and any subdomains (ie foo.example.com). The opposite is not true however. In other words if you set a cookie for example.com it will be included in any requests made to foo.example.com. However a cookie set for foo.example.com will not be included in a request to example.com.

If foo.example.com does not need the cookies set for example.com then you are just wasting network traffic. A common solution is to use www. example.com in place of example.com

yet I am still confused as to why that site above reacts differently with or without the 'www" because of this

DNS servers do NOT "automagically" add the "www" CNAME, you have to instruct the server to add it or add it manually.

You can of course add it into your control panel templates as a default.

Originally Posted by chrishirst

DNS servers do NOT "automagically" add the "www" CNAME, you have to instruct the server to add it or add it manually.

You can of course add it into your control panel templates as a default.

Oh okay got it, thank you.

www is simply a subdomain, like docs.google.com or even tycoontalk.freelancer.com. Going to http://www.tycoontalk.freelancer.com will redirect you to the correct URL because the www is not needed.

True but the canonical redirect from "www" to root has to be added by some other means, otherwise requesting www,tycoontalk.freelancer.com would deliver the same content as tycoontalk.freelancer.com does with a HTTP 200 response