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
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
Am 31.07.2011 01:05, schrieb Always Learning:
On Sat, 2011-07-30 at 19:12 +0200, Alexander Dalloz wrote:
.... www is typically just an A record and not a subdomain.
Why is it not a sub-domain ?
A subdomain would have their own zone and could be delegated.
Alexander
On Sun, 2011-07-31 at 01:20 +0200, Alexander Dalloz wrote:
Am 31.07.2011 01:05, schrieb Always Learning:
On Sat, 2011-07-30 at 19:12 +0200, Alexander Dalloz wrote:
.... www is typically just an A record and not a subdomain.
Why is it not a sub-domain ?
A subdomain would have their own zone and could be delegated.
Ah, a true sub-domain.
Thank you.
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.
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.
On Sat, 2011-07-30 at 19:15 +0200, Leonard den Ottolander wrote:
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.
Lekker ananas.
I get an instant email for each attempt.
All 404's (and other errors) are instantly scanned and when its definitely a deliberate hacking attempt the .htaccess is modified to block the hackers IP.
This domain is clearly separate from http://www.ottolander.nl.
Yes, you look very handsome :-)
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 Sat, 30 Jul 2011, Bart Schaefer wrote:
To: CentOS mailing list centos@centos.org From: Bart Schaefer barton.schaefer@gmail.com Subject: Re: [CentOS] www.mydomain.org and mydomain.org should resolve to the same IP
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.
I think the generally accept convention now is that www.domain.org and domain.org both point to the website for that particular domain name.
That's the beauty of having a domain name that allows one to create sub-domains. Not all domain name seller's provide that option of creating your own sub-domains. My karsites.net domain is registered and hosted by my ISP, but I recently moved the DNS entries for that domain name (karsites.net) to my cloud hosting provider.
I can now administer all my sub-domain entries directly on the cloud, even though I did not register the domain name there.
Being able to create many more sub-domains on a single domain obviously means you only pay for the initial domain name registration, and you can then create as many other subdomains as you need. Take sourceforge.net for example. Each project has it's own sub-domain under project-home.sf.net
Anyway, I'm bantering on, and going a bit OT now!
Kind Regards,
Keith
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
On Sat, 2011-07-30 at 10:17 -0700, Bart Schaefer wrote:
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.
By HTTP I assume you mean by coding on the web page. If so, there is an alternative method, in the configuration file for the virtual domain.
I redirect web spammers to a Chinese site :-)
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.
At Sat, 30 Jul 2011 12:55:33 -0400 CentOS mailing list centos@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@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@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sat, Jul 30, 2011 at 01:45:15PM -0400, Robert Heller wrote:
At Sat, 30 Jul 2011 12:55:33 -0400 CentOS mailing list centos@centos.org wrote:
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.
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
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
This is the correct answer; "some do, some don't". It's perfectly possible to have the domain and www.domain A records point to different places, or to have them point to the same place.
HOWEVER: It's the _client_ who is requesting this. They want both domains to go to the same web site. If you're not using the domain A record for anything else, then just do it. If you're using the A record for other reasons then perhaps put up a redirect or explain to the client the consequences of changing the A record.
Basically, with no good reason not to, don't argue with the client :-) Only argue if you have a good reason!
Stephen Harris wrote:
On Sat, Jul 30, 2011 at 01:45:15PM -0400, Robert Heller wrote:
At Sat, 30 Jul 2011 12:55:33 -0400 CentOS mailing list centos@centos.org wrote:
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.
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
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
This is the correct answer; "some do, some don't". It's perfectly possible to have the domain and www.domain A records point to different places, or to have them point to the same place.
HOWEVER: It's the _client_ who is requesting this. They want both domains to go to the same web site. If you're not using the domain A record for anything else, then just do it. If you're using the A record for other reasons then perhaps put up a redirect or explain to the client the consequences of changing the A record.
Basically, with no good reason not to, don't argue with the client :-) Only argue if you have a good reason!
Thanks for all your comments - I hear the consensus is no technical reason to have them the same, but probably safest for the great unwashed using the internet to have them go to the same site. We'll see if we can make is happen without any trauma.
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>
On Sat, 2011-07-30 at 16:49 -0700, John R Pierce wrote:
<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>
You can amalgamate that into a single entry .....
<VirtualHost astronomy.santa-cruz.ca.us:80 \ www.astronomy.santa-cruz.ca.us:80 \ astro.santa-cruz.ca.us:80 \ www.astro.santa-cruz.ca.us:80> DocumentRoot /data/web/astronomy ServerName astronomy.santa-cruz.ca.us CustomLog /data/logs/acc.astronomy combined ErrorLog /data/logs/err.astronomy DirectoryIndex main.php HostnameLookups Off </VirtualHost>
On Sun, Jul 31, 2011 at 1:42 PM, Always Learning centos@u6.u22.net wrote:
On Sat, 2011-07-30 at 16:49 -0700, John R Pierce wrote:
<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>
You can amalgamate that into a single entry .....
<VirtualHost astronomy.santa-cruz.ca.us:80 \ www.astronomy.santa-cruz.ca.us:80 \ astro.santa-cruz.ca.us:80 \ www.astro.santa-cruz.ca.us:80> DocumentRoot /data/web/astronomy ServerName astronomy.santa-cruz.ca.us CustomLog /data/logs/acc.astronomy combined ErrorLog /data/logs/err.astronomy DirectoryIndex main.php HostnameLookups Off
</VirtualHost>
Or use ServerAlias (not tested).
Cheers,
Cliff
On Sun, 2011-07-31 at 13:47 +1200, Cliff Pratt wrote:
On Sun, Jul 31, 2011 at 1:42 PM, Always Learning centos@u6.u22.net wrote:
On Sat, 2011-07-30 at 16:49 -0700, John R Pierce wrote:
<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>
You can amalgamate that into a single entry .....
<VirtualHost astronomy.santa-cruz.ca.us:80 \ www.astronomy.santa-cruz.ca.us:80 \ astro.santa-cruz.ca.us:80 \ www.astro.santa-cruz.ca.us:80> DocumentRoot /data/web/astronomy ServerName astronomy.santa-cruz.ca.us CustomLog /data/logs/acc.astronomy combined ErrorLog /data/logs/err.astronomy DirectoryIndex main.php HostnameLookups Off
</VirtualHost>
Or use ServerAlias (not tested).
John used 'ServerAlias' and look at all the extra lines required. Don't forget the computer is supposed to work for the man (and woman) not vice versa !
On 07/30/11 6:42 PM, Always Learning wrote:
You can amalgamate that into a single entry .....
that doesn't do the redirect. I *want* it so that if you go to any of these URLs...
http://astro.santa-cruz.ca.us http://www.astro.santa-cruz.ca.us http://www.astronomy.santa-cruz.ca.us
you get redirected to http://astronomy.santa-cruz.ca.us
try it, you'll see how that works.
On Sun, Jul 31, 2011 at 2:39 PM, John R Pierce pierce@hogranch.com wrote:
On 07/30/11 6:42 PM, Always Learning wrote:
You can amalgamate that into a single entry .....
that doesn't do the redirect. I *want* it so that if you go to any of these URLs...
http://astro.santa-cruz.ca.us http://www.astro.santa-cruz.ca.us http://www.astronomy.santa-cruz.ca.us
you get redirected to http://astronomy.santa-cruz.ca.us
try it, you'll see how that works.
Yeah, I was suggesting something like this:
<VirtualHost 207.111.214.244> ServerName astronomy.santa-cruz.ca.us ServerAlias astro.santa-cruz.ca.us ServerAlias www.astronomy.santa-cruz.ca.us ServerAlias www.astro.santa-cruz.ca.us
DocumentRoot /..../html ErrorLog /...../logs/error_log CustomLog /..../logs/access_log common </VirtualHost>
or
<VirtualHost 207.111.214.244> ServerName astronomy.santa-cruz.ca.us # All aliases on one long line ServerAlias astro.santa-cruz.ca.us www.astronomy.santa-cruz.ca.us www.astro.santa-cruz.ca.us
DocumentRoot /..../html ErrorLog /...../logs/error_log CustomLog /..../logs/access_log common </VirtualHost>
I *think* the first example works, but I'd have to check the configs to be sure and I don't have access from here.
However, if it works for you, it works, and all else is quibbles.
Cheers,
Cliff
On Sat, 2011-07-30 at 19:39 -0700, John R Pierce wrote:
On 07/30/11 6:42 PM, Always Learning wrote:
You can amalgamate that into a single entry .....
that doesn't do the redirect. I *want* it so that if you go to any of these URLs...
http://astro.santa-cruz.ca.us http://www.astro.santa-cruz.ca.us http://www.astronomy.santa-cruz.ca.usyou get redirected to http://astronomy.santa-cruz.ca.us
try it, you'll see how that works.
Instead of being 'redirected' why not go straight to the required web site http://astronomy.santa-cruz.ca.us whatever you enter:-
http://astro.santa-cruz.ca.us http://www.astro.santa-cruz.ca.us http://www.astronomy.santa-cruz.ca.us http://astronomy.santa-cruz.ca.us
?
Why make two moves when one is sufficient ?
On 07/31/2011 05:07 AM, Always Learning wrote:
On Sat, 2011-07-30 at 19:39 -0700, John R Pierce wrote:
On 07/30/11 6:42 PM, Always Learning wrote:
You can amalgamate that into a single entry .....
that doesn't do the redirect. I *want* it so that if you go to any of these URLs...
http://astro.santa-cruz.ca.us http://www.astro.santa-cruz.ca.us http://www.astronomy.santa-cruz.ca.usyou get redirected to http://astronomy.santa-cruz.ca.us
try it, you'll see how that works.
Instead of being 'redirected' why not go straight to the required web site http://astronomy.santa-cruz.ca.us whatever you enter:-
http://astro.santa-cruz.ca.us http://www.astro.santa-cruz.ca.us http://www.astronomy.santa-cruz.ca.us http://astronomy.santa-cruz.ca.us?
Why make two moves when one is sufficient ?
Because once people link to the site or bookmark it using all four domains you essentially have to maintain all four domains for the rest of the live of the site i.e. through redesigns, restructurings, moves, etc.
The better approach is to declare one domain as canonical and redirect all other domains to it.
Also Google can reduce your page rank if it find the same content under multiple domains because it thinks you are cheating. Nowadays Google is supposed to be smart about this and doesn't count www.* vs non-www.* as duplicate content but the exact rules how Google determines this are not known.
Regards, Dennis
On Sun, 2011-07-31 at 13:41 +0200, Dennis Jacobfeuerborn wrote:
On 07/31/2011 05:07 AM, Always Learning wrote:
On Sat, 2011-07-30 at 19:39 -0700, John R Pierce wrote:
On 07/30/11 6:42 PM, Always Learning wrote:
You can amalgamate that into a single entry .....
that doesn't do the redirect. I *want* it so that if you go to any of these URLs...
http://astro.santa-cruz.ca.us http://www.astro.santa-cruz.ca.us http://www.astronomy.santa-cruz.ca.usyou get redirected to http://astronomy.santa-cruz.ca.us
try it, you'll see how that works.
Instead of being 'redirected' why not go straight to the required web site http://astronomy.santa-cruz.ca.us whatever you enter:-
http://astro.santa-cruz.ca.us http://www.astro.santa-cruz.ca.us http://www.astronomy.santa-cruz.ca.us http://astronomy.santa-cruz.ca.us?
Why make two moves when one is sufficient ?
Because once people link to the site or bookmark it using all four domains you essentially have to maintain all four domains for the rest of the live of the site i.e. through redesigns, restructurings, moves, etc.
Please kindly excuse any misunderstanding I may appear to exhibit.
My Point Number 1: ONE web site.
My Point Number 2: 4 different web site addresses go automatically to the ONE web site.
My Point Number 3: no redirection just straight to the single web site.
My Point Number 4: This works well for me in Apache 2.
Thus the only maintenance is:-
(5) one web site.
(6) 4 DNS A records pointing to the same IP address
The better approach is to declare one domain as canonical and redirect all other domains to it.
I simply use 'A' records pointing to the same IP address.
Also Google can reduce your page rank if it find the same content under multiple domains because it thinks you are cheating. Nowadays Google is supposed to be smart about this and doesn't count www.* vs non-www.* as duplicate content but the exact rules how Google determines this are not known.
In the 10 years I have seriously hosted several personal web sites, I have neither cared about Google ratings not sought to enhance the position in search engine listings. However, much to my surprise, I am top of the Google listing for some searches and within the top 5 for others.
I really do not care about being rated. I never worry about visitors because they come if they want to. The negative side of running personal web sites, circa 8,000 pages, is the maintenance effort whilst creating new pages and writing the content and doing other unrelated tasks.
On 07/31/11 6:28 AM, Always Learning wrote:
Please kindly excuse any misunderstanding I may appear to exhibit.
as Peter says, I intentionally set it up this way so that no matter which alias you go to, you END UP with the preferred URL for bookmarking, etc. This also makes the internal page caching on my site work better... on this drupal built site, ALL the pages are dynamically generated content, but when anonymous users visit common pages, they'll get the cached last value. the caching is by full URL, so forcing all users to use the canonical form ensures maximum effectiveness.
On Sun, 31 Jul 2011, John R Pierce wrote:
To: centos@centos.org From: John R Pierce pierce@hogranch.com Subject: Re: [CentOS] www.mydomain.org and mydomain.org should resolve to the same IP
On 07/31/11 6:28 AM, Always Learning wrote:
Please kindly excuse any misunderstanding I may appear to exhibit.
as Peter says, I intentionally set it up this way so that no matter which alias you go to, you END UP with the preferred URL for bookmarking, etc. This also makes the internal page caching on my site work better... on this drupal built site, ALL the pages are dynamically generated content, but when anonymous users visit common pages, they'll get the cached last value. the caching is by full URL, so forcing all users to use the canonical form ensures maximum effectiveness.
Makes perfect sense to me. Once a visitor hits your website using a name-based virtual-host domain name, then Apache will continue to use that name for the rest of their visit.
So redirecting to the domain name of your choice deals with the aforementioned issues, even though it might be a little bit more complicated to set up - not that much though ;)
BTW - without putting this thread into OT territory, have you seen TEXTPATTERN CMS? Well worth taking a look at. It's GPL'd OSS, with a great community of developers and contributors. Disputed to be 'THE' only CMS you'll ever want to use.
The Many Reasons to use Textpattern
With a browser-based interface in over 40 languages, excellent support and full range of features, it's no wonder that publishers, designers and developers everywhere choose Textpattern.
Textpattern is For Publishers:
* Direct, easy to follow interface - "just write" * Fast, intuitive editing of articles, links, comments, page elements * Quick conversion of plain text to valid XHTML with Textile * Upload and organise images and files via browser * More reasons to use Textpattern!
Textpattern is For Designers:
* Fast copy/paste of plugins to extend TXP's capabilities * Supported by development team and community on lively forum * Standards compliant by default * No limit to style, layout or sections * More reasons to use Textpattern!
Also take a look at the links in the LH menu, under 'External Textpattern Links'
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
On 7/31/11 8:28 AM, Always Learning wrote:
Because once people link to the site or bookmark it using all four domains you essentially have to maintain all four domains for the rest of the live of the site i.e. through redesigns, restructurings, moves, etc.
Please kindly excuse any misunderstanding I may appear to exhibit.
My Point Number 1: ONE web site.
My Point Number 2: 4 different web site addresses go automatically to the ONE web site.
My Point Number 3: no redirection just straight to the single web site.
My Point Number 4: This works well for me in Apache 2.
Thus the only maintenance is:-
(5) one web site.
(6) 4 DNS A records pointing to the same IP address
The better approach is to declare one domain as canonical and redirect all other domains to it.
I simply use 'A' records pointing to the same IP address.
There are several situations that make this not work as well as redirecting to a canonical name. Any external caches (like a squid on the client site) will keep separate copies for each name accessed through it. If the client authenticates and then is redirected to one of the other names (and there are likely scenarios for that if your site has/needs any absolute references to itself) the user will have to authenticate again when the site name changes. Likewise, cookies are connected to the name and sessions may act strangely if you jump to a different name even though it is the same server.
In the 10 years I have seriously hosted several personal web sites, I have neither cared about Google ratings not sought to enhance the position in search engine listings. However, much to my surprise, I am top of the Google listing for some searches and within the top 5 for others.
You only care about that if you are selling ads directly or want the additional traffic that a top rating will get.
It is fairly simple to do the redirects - just have the default virtual server in your apache config use a stack of rewriterule based redirects using regexps to match the possible host names they might have used and redirect to the correct target. This also makes it easy to move individual sites off to different servers when they outgrow a single host or a different set of people needs to manage it.
-
Alexander Dalloz -
Always Learning -
Bart Schaefer -
Cliff Pratt -
Dennis Jacobfeuerborn -
Digimer -
John R Pierce -
Keith Roberts -
Leonard den Ottolander -
Les Mikesell -
Rob Kampen -
Robert Heller -
Stephen Harris