Talk:Subdomain

message: Putting in extra citations would not help; requesting them is simply calling in to question the validity of what is being said, but I think it does a great job of reflecting the discussion below.  Perhaps a discussion of "nominal" use of subdomains would make a good start, which is flagged as being nominal and therefore not always true, followed by a discussion of how the providers muck it up with examples?  — Preceding unsigned comment added by 109.145.28.236 (talk) 11:13, 5 December 2016 (UTC)
thread_title:  The discussion of domains and subdomains is the most helpful thing I have found =

message: Would recommend that the discussion of alternate uses of "vanity domain" be moved into a separate article to avoid confusion.
I feel this page is absolutely in error to include the negative stuff about vanity domains and its definitions.  Has nothing of value in telling us what a subdomain is.  My subdomains don't fit those definitions, e.g. wiki.*, ftp.*, map.*, www.*
Motivations have nothing significant to do with what functionality is obtained with subdomains.
The section on subdomain shortening services should be removed, it has nothing to do with defining subdomains and appears to be more misguided negative discussion about vanity domains and their affects.  An article on URL substitution might house it.
:The root cause is the fact that somebody made vanity domain into a redirect to this article, which then necessitates that some mention of its alternate meanings be included.  Maybe it should be separated out. *Dan T.* 17:56, 25 November 2006 (UTC)
replies: text: Done. I've added some content; check it over kthx. EdC 19:13, 4 December 2006 (UTC)

text: I have added "Vanity_domain" to the See Also list. I think the corresponding content in the main article can be deleted but I am not sure ho to do that.
Sam Tomato (talk) 15:24, 25 November 2011 (UTC)
thread_title:  Discussion of "vanity domain" 

message: The Link Domain Names - Implementation and Specification in the External Links section is broken.
Regards,
Siddhesh
Fixed to point to the IETF RFC server. 198.51.119.130 18:03, 9 August 2006 (UTC)
thread_title:  Broken Link in External Links  Section 

message: Real simple,  www.yahoo.com:
www = subdomain or third level domain
yahoo = domain name
com = top level domain or TLD
This article is inaccurate and is in need of a rewrite.
: Yes, and all are subdomains of of their parent domain.  DNS is hierarchical, and the term expresses a relation within that hierarchy.  Note that your three-level scheme doesn't apply to gSLD-allocated names. –EdC 00:34, 15 July 2007 (UTC)
replies: text: Evidently you don't have time to correctly spell your unattributed contributions either. EdC 01:58, 1 December 2007 (UTC)

text: This is completely incorrect. All of the above except for "." are subdomains. ".com." is a subdomain of ".", "yahoo.com." is a subdomain of ".com.", and "www.yahoo.com." could be a subdomain of "yahoo.com." IF there are NS records delegating it to some nameserver(s), which there aren't, so it isn't. Kelt65 (talk) 20:09, 7 July 2016 (UTC)
thread_title:  Validity of information in question 

message: A subdomain is not something like support.example.com.  That's a Hostname.  A case in which support.example.com would be a subdomain is if you had hostname records within it, like www (www.support.example.com), printers (printers.support.example.com) and so on.  The support.example.com may also be an A record, which is called the domain A record, but that's different. People keep calling things subdomains when they aren't really and its confusing to people who know.  This article only furthers that confusion by using examples like en.wikipedia.org being a subdomain.  It is not, thats a hostname.  So I'd like to get a consensus here before changing the article. -- Suso 19:19, 30 November 2007 (UTC)
replies: text: Well, this article is in much need of references.  That said, all the RFCs (RFC 1034, RFC 1035, etc.) support the articles discussions about what is and is not a subdomain.  In the last paragraph of RFC 1034 section 3.1. "Name space specifications and terminology", it gives a fairly clear explanation of a subdomain, which matches this article.  As another example, RFC 1035 section 2.3.1 gives the ANBF for a subdomain which matches this article's usage.  Domains such as support.example.com indeed also subdomains.  Having A records is not what makes something a domain.  Can you please give citations from the DNS RFCs that contradict what this article says?  Wrs1864 21:03, 30 November 2007 (UTC)

text: What Wrs1864 said.  support.example.com. is clearly a subdomain, because it is a domain name identifying a domain, and is not the root.  Assuming it has an A (or AAAA) record, it is also a hostname, but it is not required to be.  Please read the relevant RFCs before setting yourself up as an expert. EdC 01:56, 1 December 2007 (UTC)

text: What on earth? "support.example.com" can be either a FQDN of a host or a domain name. It is not all at "clearly a subdomain". The only thing certain you may infer is that "example.com" is a domain. There is no difference between a subdomain and a domain unless the domain is the top level root domain, ".". All domains are subdomains of the root. All subdomains are also domains. A domain, or a subdomain, must have a delegation (NS records) for it to be a "domain", otherwise, it is something else. It is true that webhosting companies have polluted the language here by calling host records "subdomains". The article is correct as it stands today. Kelt65 (talk) 20:18, 7 July 2016 (UTC)
thread_title:  This article is misleading 

message: The way this article reads, it seems as though if a website goes down, the websites that are hosted on it also go down, however there are 2 notable exceptions to this, Doom WAD Station and Mancubus.net are currently down websites.  However some example.mancubus.net and example.doomwadstation.com (as well as [[doomwadstation.com/example and mancubus.net/example are still up, yet their websites are 404.  —Preceding unsigned comment added by 4.244.33.220 (talk) 13:26, 1 June 2008 (UTC)
replies: text: From my reading of the article, it doesn't appear to address such issues at all.  In any case, there is a distinction between fundamental Internet services such as DNS and application-level services such as HTTP; a site's DNS can well be responding fine even when some of its HTTP services are unavailable. EdC (talk) 18:10, 1 June 2008 (UTC)
thread_title:  false information 

message: Can someone please tell me how the www. subdomain works(if it even is a subdomain) is it right to imagin the "subdomain tree" like this:
              com
               |
           example.com
               |
           ---------
          |         |
 sub.example.com   www.example.com
       |
 www.sub.example.com
(sorry for my bad looking ASCII tree drawing :P)
or is the www. subdomain something more than a regular subdomain?--Ismetteren (talk) 17:11, 17 May 2009 (UTC)
replies: text: In your example above, www.example.com is considered a subdomain as far as this article and DNS theory goes. For almost every domain out there, www will have an A record associated with it that points to the IP address of a web server (or a CNAME that points to a domain name that resolves to a webserver). One thing to remember is that, although most websites are accessed by going to www.somedomain.sometld , this is only due to a generally accepted naming convention and is not strictly enforced by DNS itself. So there is no special external www service, container, or ruleset. Each DNS zone file can define www as whatever it wants, or as nothing at all... I can make www.mydomain.com go to a FTP service or a mail server if I want to (it just wouldn't make a lot of sense), or I can leave it completely undefined and use http://website.mydomain.com instead as the URL for loading a website within mydomain.com -- Dgmackay (talk) 23:28, 9 June 2009 (UTC)

text: Perhaps it makes more sense as a tree, which is what the DNS is -
  .                            # root domain
  └── com                      # com domain/tld
      └── example              # domain, subdomain of .com
          ├── sub              # domain, subdomain of .example.com
          │   └── www          # indeterminate, could be host name or domain
          └── www              # indeterminate, could be host name or domain
We know "sub.example.com" is indeed a domain as the existence of the record "www.sub.example.com" requires it.
Kelt65 (talk) 20:27, 7 July 2016 (UTC)
thread_title:  www. ??? 

message: If you create a directory that contains a html file named "index" it will act like a subdomain or separate site (e.g. typing www.flamingrose.org/lojong into your browser will automatically open the index file in the directory lojong of the site www.flamingrose.org.) Obviously adding the index file makes the directory lojong something different than a regular directory -- does anyone know what such a directory is called?
-- Preceeding unsigned comment added by 98.162.137.62 on 05:30, 12 January 2016‎
: Directories are unrelated to subdomains. What you're describing is just called a directory's index page. What file you use depends on the server configuration, e.g. in Apache, "DirectoryIndex index.php index.html index.htm" in the httpd.conf or .htaccess file tells Apache to look first for index.php, then index.html, then index.htm in the directory. If none of those are found, it'll standardly default to giving a directory listing (unless that's been disabled through any of various means). You could set your server to use any file, e.g. with a directive like "DirectoryIndex foo.txt".  —Undomelin (talk) 22:08, 16 March 2018 (UTC)
thread_title:  Name for a directory that acts like a subdomain?