Am 30.07.2011 18:55, schrieb Rob Kampen: > Hi list, > I am having a debate with one of my clients where I administer their > domain and storage server but the website is hosted by godaddy. > thus www.mydomain.org goes to one of godaddy's servers but the > mydomain.org and mail.mydomain.org and ns1.mydomain.org all go elsewhere. > > My website designer has been convinced by the godaddy web design team > that we should > <quote> > > Again, the standard practice in the industry is for name.org and > www.name.org to be "tied" together. The primary domain is mydomain.org > and you > have it while the church's web site is using the sub domain, > www.mydomain.org. I > have been on the phone with tech support and they say that out of close > to 1 > million web site hosting customers, NOBODY purposely separates the two. We > will run into these issues every time someone tries to create a form, new > navigation and potentially new pages, according to Godaddy. > PLEASE create a sub-domain for your server that is not mydomain.org and, > transfer mydomain.org into the new godaddy account we just set up for > the new > web site. > > </quote> > I have never heard this before, and have not had any problems with any > other clients until this client hooked up with godaddy for their website. > Anyone out there that can shed some light on this? > Do most domains keep the Top Level Domain (TLD) the same as the www.TLD? > > TIA > Rob Well, using something like an A record or CNAME like www.domain.tld is something coming from the old days of internet, where people thought it would be good practice to have a hostname target which reflects the type of service behind it. www for websites, ftp for an FTP service and so on. Nowadays, at least in the area of accessing webpages, most people are common to access a page by just entering the domain name, like google.com or yahoo.com. Typically www.google.com works as well, just to serve both tastes and to avoid unnecessary hurdles. Said so, technically there is no need that www.domain.tld has to resolve to the same IP target as domain.tld. But keeping them together serves the customers of web services better as they do not have to think about it. Btw., the TLD is not domain.com or such, but com or org or us. domain is the domain name, and www is typically just an A record and not a subdomain. Regards Alexander