SEO Hosting - Name Server question

[burnsai]

So, I have an account at SeoHosting. I just bought 10 more c class ips which brings my total up to 20. I have about 150 websites spread out over the 1st 10 ips and am just starting to populate the second 10 ips with new sites.

I purchase my domain names with various providers, godaddy, bluehost, hostingdude etc. But I always use the same name servers to point the domain to my SEO Hosting account. Something like:

xxx1.websitewelcome.com
xxx2.websitewelcome.com

My question is - can google track down my network of sites and deduce that they are all owned by the same person if I continue to use the same Name Servers? Because that would be a real bummer.


SEO Hosting advertises:

Separate C Class Nameservers
Private Branded Nameservers

But no one at Seo Hosting seems to understand what that means. The problem is, neither do I! So, I don't even know the right questions to ask.

So, my second question is - if I should use different name servers, how would I do it?

Thanks

[Ebo Etoyep]

Originally Posted by burnsai

So, I have an account at SeoHosting. I just bought 10 more c class ips which brings my total up to 20. I have about 150 websites spread out over the 1st 10 ips and am just starting to populate the second 10 ips with new sites.

I purchase my domain names with various providers, godaddy, bluehost, hostingdude etc. But I always use the same name servers to point the domain to my SEO Hosting account. Something like:

xxx1.websitewelcome.com
xxx2.websitewelcome.com

My question is - can google track down my network of sites and deduce that they are all owned by the same person if I continue to use the same Name Servers? Because that would be a real bummer.


SEO Hosting advertises:

Separate C Class Nameservers
Private Branded Nameservers

But no one at Seo Hosting seems to understand what that means. The problem is, neither do I! So, I don't even know the right questions to ask.

So, my second question is - if I should use different name servers, how would I do it?

Thanks

I wouldn't worry too much about Google using nslookup to track down your site network, though it certainly wouldn't be too hard if they were in the practice of doing that. With the websitewelcome.com nameservers, you are at least mixed in with a large group of other people hosted with HG.

I believe Matt Cutts and other Google employees have stated publicly that they do not care about nameservers and the like and that it doesn't play a role in ranking. Whether or not that is actually true is anyone's guess, I suppose, but it is straight from the horse's mouth.

A private branded nameserver basically allows you to setup nameservers at XXX.somedomain.com rather than using their websitewelcome.com nameservers. This is commonly used by resellers who don't want their clients to effectively "cut out the middle man." If you're concerned about G tracking your site network via nslookup, you probably don't want your own branded nameservers. Separate c-class nameservers would just distribute the IP's used by your nameservers. IMHO, paying for separate c-class nameservers seem silly as they'll both come up in a simple nameserver lookup REGARDLESS of their IP addresses.

[digitalproductreporter]

I wouldn't waste my money on unique ip's just to keep the same name server for all of them. that pretty much says we are all related.

I would do this by opening 10 shared accounts at different budget hosts for like $5 or $10 per month each

not only will they be different nameservers, they'd be different locations around the globe and really different makeups

[thecableguy]

Here's part of the welcome email setup instructions:

***SETUP INFO***
When you login to http://68.46.153.2/whm (change to your URL) please follow the below steps:

1) Create a new package. Go to "Packages" and then "Add Packages".
Set a package name and fill in the features as you need.
Make sure you select the "Dedicated IP" option. Next, click add.

2) Create your account. Go to "Account Functions" and then to "Create a New Account".
Fill in your account's domain, username and password and then go down a few fields to "package"
and select the package that you created in Step 1. Ensure that the "IP" option is enabled
below the quota field. Go ahead and Select an Ip Address and change it
from "--Auto Assign--" to an IP that you have not used. Next, click create.

3) Make sure the domain you created is pointed using either the nameservers above or private nameservers.
Give your new domain some time to propagate and you'll be all set!

[ed41143]

It is always better to space out, so to speak, your sites, like above stated, then they show up from all over the globe and I would highly expect them to much better situated that way, wouldn't you?