CentOS - Jul 2011 - www.mydomain.org and mydomain.org should resolve to the same IP

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rkampen.vcf
Type: text/x-vcard
Size: 322 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20110730/43fda683/attachment-0001.vcf>

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

On 07/30/2011 12:55 PM, 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?
> 
> TIA
> Rob
With no comment related to GoDaddy itself; I do keep www.domain.tld and
domain.tld pointing to the same page, and I get quite frustrated when
sites don't do that. When I am typing a URL, I find the need to type the
'www.' prefix superfluous and annoying.

-- 
Digimer
E-Mail:              digimer at alteeve.com
Freenode handle:     digimer
Papers and Projects: http://alteeve.com
Node Assassin:       http://nodeassassin.org
"At what point did we forget that the Space Shuttle was, essentially,
a program that strapped human beings to an explosion and tried to stab
through the sky with fire and math?"

Hello Rob,

On Sat, 2011-07-30 at 12:55 -0400, Rob Kampen wrote:
> <quote>
> 
> Again, the standard practice in the industry is for name.org and
> www.name.org to be "tied" together.
True, standard practice, but that doesn't mean that it *has* to be done
like this.
> they say that out of close to 1
> million web site hosting customers, NOBODY purposely separates the two.
I do, I do! ;)

Cause most people probably aren't knowledgeable enough or don't have the
need to do so.
>  We
> will run into these issues every time someone tries to create a form, new
> navigation and potentially new pages, according to Godaddy.
Which issues? If you remove the ServerAlias from the apache config these
domains can be safely separated, even on IP if you wish.

I'm hosting a kind of fall back page at http://ottolander.nl which is
what shows up if someone tries to access one of the virtual hosts by IP.
This domain is clearly separate from http://www.ottolander.nl.

Regards,
Leonard.

-- 
mount -t life -o ro /dev/dna /genetic/research

It's extremely common for an HTTP connection to the unqualified
first-level domain to direct one to the website home page, but whether
that is accomplished by having the IPs be the same or by way of an
HTTP redirect, I would not say there's any clear winner.   However, it
is not a universal practice.

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

At Sat, 30 Jul 2011 12:55:33 -0400 CentOS mailing list <centos at
centos.org> 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?
Some do, some don't.  Some have a redirect from TLD to www.TLD, some
have a redirect from www.TLD to TLD, some allow www.TLD and TLD to be
used interchangably (eg have set Apache to consided one an alias for
the other without any redirect directives).  There is NO hard and fast
rule for this.  And still others have various <mumble>.TLD, in some
cases several *different* servers (physical or virtual), all running a
httpd server daemon (static.TLD, images.TLD, www.TLD ... -- visit
www.facebook.com and watch the status bar on your browser for
enlightenment). 

I think Firefox (maybe IE) will automagically stick www. on front of a
domain name when it is entered in the location field and the bare domain
name fails to resolve to an IP number.
> 
> TIA
> Rob
> 
> 
> begin:vcard
> fn:Rob Kampen
> n:Kampen;Rob
> org:Team Torman Realty, LLC
> adr:;;13019 Water Point Blvd;Windermere;FL;34786;USA
> email;internet:rkampen at reaching-clients.com
> tel;work:407-876-4108
> tel;fax:407-876-3591
> tel;home:407-876-4854
> tel;cell:407-341-3815
> note:LCAM & CPM Candidate
> url:www.robkampen.com
> version:2.1
> end:vcard
> 
> 
> MIME-Version: 1.0
> 
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 
>                                                                       
-- 
Robert Heller             -- 978-544-6933 / heller at deepsoft.com
Deepwoods Software        -- http://www.deepsoft.com/
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments

On 07/30/11 9:55 AM, Rob Kampen wrote:
> Again, the standard practice in the industry is for name.org and
> www.name.org to be "tied" together. 
if the domain is primarily a website, for sure, in fact, many of my 
websites prefer domain.com to www.domain.com and in fact, I redirect the 
latter to the former...

example domain:

<VirtualHost  207.111.214.244>
         ServerName astronomy.santa-cruz.ca.us
         DocumentRoot /..../html
         ErrorLog /...../logs/error_log
         CustomLog /..../logs/access_log common
</VirtualHost>

<VirtualHost 207.111.214.244>
         ServerName astro.santa-cruz.ca.us
         ServerAlias www.astronomy.santa-cruz.ca.us 
www.astro.santa-cruz.ca.us
         RedirectMatch permanent /(.*) http://astronomy.santa-cruz.ca.us/$1
</VirtualHost>



-- 
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast