Is xxx.domain.com and www.domain.com the same?
 

I just looked at one of my sponsors and I have a few hits coming from xxx.mydomain.com/ It looks just like www.mydomain.com and has all my link codes and everything.

Is the adult industry going to xxx instead of www or what is going on? I am a bit confused, I though that the xxx issue did not pass.

Are you sure it isn't www.xxx.mydomain.com/?

Check it out: http://xxx.xdame.com/ and http://www.xdame.com/

What do you think?

Tek. I think its just a sub domain for xdame.com. Because if you look at http://www.xxx.xdame.com/ its the same homepage as http://xxx.xdame.com as well as the main URL http://www.xdame.com It's someones nice marketing strategy I think.

J-

|jester|

Looks like it's just a subdomain to me? See...

http://www.xxx.xdame.com/

Well, who would set it up? I own that domain and I don't have any subdomains set up.

Hmm, now thats a mystery. Have you logged into your hosting service? Is there a sub domain there? Could your host have set it up because it is an adult site? I wouldnt really know how that could happen without you doing it or someone authorized by you.

J -

|jester|

Loged in and checked, no subdomain is set up. |huh

Maybe cd34 can shed some light into this.

Thats very odd, I am assuming that you don't have any of your incoming links or reciprocals set to goto www.xxx.xdame.com that they all point to www.xdame.com ..And all your own codes are still intact on this xxx.domain? Thats odd. I would think if someone were trying to hi-jack you they'd replace your codes with theirs? Very strange..I've never heard of such a thing nor have I experienced it.

Sorry I can't be of more help.

J -

|jester|

It's something to do with your hosting, not the adult passing the .xxx extensions. Those were going to replace the .coms not the www part.

Basically, it looks like the sub is just a mirror of your main site for some reason...?

Ok, very good chance you host has a client who has signed up with the domain as xxx.mydomain.com.
Most times a host will pick up on this and prevent it from happening, however in an automated smaller (or less observant) host example the account may be overlooked.
Have you done a ping on both addresses and determined if there is two different IP addresses. If they are the same, the two sites are hosted on the same server, if they are different there is either something in your domain config (Host Records) or there is something in cPanel DNS (if you are using it)

or.... you (for some reason) have wildcard DNS added to your http server config. i.e abcd.domain.com and qwer.domain.com (or anything else you can think of .domain.com) will load the same website

Update: Yes you DEFINITELY have wildcard DNS activated, i just tried http://abc.xdame.com/ and it is the same site :D

Nice find. |thumb

seems like your hosting is redirecting all nonexisting domains to www. you can put anything infront of the domain name and it would still load the main page

Good look r18..Iev heard and have been optioned to use wildcard DNS but never saw it in action. Is this a good thing?

J-

|jester|

Yup for sure, I just used babes.xdame.com and it showed the main site content.

J-

|jester|

Thanks for shading some light into this. I was getting a bit worried. :D

I only use it for one purpose and thats for the Strongbox security software.

can be. I've used it before for websites (such as DKP hosting - think WoW) and with a .htaccess file could load different settings based on the subdomain called. Essentially using one install of a piece of software but loading different configs from subdomains.

As for a good thing in the sense of our type of content... Probably not, but then I could be wrong. Your content 'could' be classed as duplicate, and as such could suffer a penalty in SEs (or even flagged as copied).

But it 'could' also be used (in conjuction with htaccess or smart coding) to deliver different content. For example, I am playing with the idea of seperating out my TGP/MGP by using wildcard DNS.
babes.mysite.com will open www.mysite.com/babes.html (or PHP) but to the end user they will still be on babes.mysite.com

Lots of stuff you can use with this, but just be aware if you are on shared or reseller hosting (and your host is an ass) you will find they will be reluctant to change the one line of code in the httpd.conf file for your domain.
VPS and Dedicated ppl, the changes are made in httpd.conf (might want to do a search for yourself where your copy is), and effectively do the following:

Find mysite.com in httpd.conf

Should look something like this:

Serveralias mysite.com
***** BLAH BLAH BLAH *****


And change the ServerAlias line to read this:
ServerAlias *.mysite.com mysite.com

Save the changes, exit the editor, then
service httpd restart

You should now be able to use 1.mysite.com, 2.mysite.com, etc. etc.

Oh and getting the subdomain when someone hits your site in PHP would look something like this:

$serverhost = explode('.',$_SERVER["HTTP_HOST"]);
$sub = $serverhost[0];
if ($sub = "www") {
$sub = "";
}
?>

There is your lengthy, and comprehensive answer for this sometimes awesome apache modification. :D

Another possible reason to use wildcards would be to avoid IE's 2 socket connection limit when hitting web sites. Briefly, IE will put 2 image requests to a hostname, and queue up the rest to be fetched as the 4 requests complete. If you use multiple hostnames, i.e. img1.domain.com, img2.domain.com, img3.domain.com, IE will request 4 connections per hostname -- even though the requests are being handled by the same server.

http://www.die.net/musings/page_load_time/

well... it seems I never thought of that one, but it definitely makes sense. I might give that one a go sometime, could be handy of TGP/MGPs with loads of thumbs

All very useful information. Definitely shed some light on a subject I didnt understand or know the dynamics of. Thanks.

J-


|jester|

I believe this is not good for SEO. Search Engines can interpret such subdomains as duplicate content and you'll receive penalties. Turn that option off or use redirects to your main site when someone enters a subdomain.