On 7/30/11 11:55 AM, Rob Kampen wrote:
> 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?
It's common practice, but not universal. And it is common for users to confuse
the two so it is a reasonable defensive practice, as is also obtaining likely
misspellings of the name. It tends to work best if the alternative names do an
http-level redirect to the name the server thinks of as its own, though, instead
of accepting them all transparently.
--
Les Mikesell
lesmikesell at gmail.com