Originally posted by: mugs
Originally posted by: LoKe
Originally posted by: Rock Hydra
Originally posted by: LoKe
Do none of you understand?
I do. I have that option in my dreamhost panel for my domain for setting up the rules for using the www. prefix.
:thumbsup:
Text
They don't seem to give any reason for leaving off the www, they just think it should be done. I think the www belongs there. A webserver can have any name, www is just the most common. For a long time Netscape's website was home.netscape.com, not
www.netscape.com.
Edit: Upon further review, I think those people are idiots.
Well, a domain should have a default server. i.e. when I nslookup scrounge.local, it gives me all the domain controllers, since those are the primary services on that domain. I can also nslookup dc1.scrounge.local - that gives me a specific domain controller.
In the case of anandech, the primary service offered on this domain is www the services provided by the server at
www.anandtech.com. Thereby, the default for the anandtech.com domain should be the same IP as the
www.anandtech.com entry.
DNS was designed as a heirarchial system with defaults - it's really up to the system administrators to determine how exactly they want to play it, but it's bad form to have the top level domain that you admin (the top level in this case is anandtech.com) not default to any particular server because that's the primary connection point. The only exception to this is the IETF, because they admin the TLDs, which have no services provided - which is why you can't nslookup com, net, org, etc.
Then again, if an unconfigured webserver is Anandtech's primary service, then they have anandtech.com configured 100% correctly.
Oh, wait, did I just give a technical answer on AT? Oops. Sorry if I made any heads explode.