If you provide resellers accounts, I'm wondering what others do for the resellers name servers. Do you assign them fresh IPs or the same IPs for all resellers? We assign shared IPs and private ones for an extra cost.

Just wondering to see how other webhosts work. :stickout:

It all depends if you provide "private label" resellers than usually the host should provide private name servers (unique IP addresses). Otherwise shared works just fine. It's just a matter of whether or not the reseller mind's being "found out" as being resellers. Most resellers don't want people to know so they can appear to not be a "starter host"

At least that's how I see it. Hope I helped bud. Have a great day!

It all depends if you provide "private label" resellers than usually the host should provide private name servers (unique IP addresses). Otherwise shared works just fine. It's just a matter of whether or not the reseller mind's being "found out" as being resellers. Most resellers don't want people to know so they can appear to not be a "starter host"

At least that's how I see it. Hope I helped bud. Have a great day!

But even if you give them private IPs they can still be found out the exact same way. It makes no difference really, could you explain how it does?

The company I go through has an IP for name servers. I point my name servers to that particular IP address. I then use their shared IP for all clients that do not require a dedicated IP address.

But even if you give them private IPs they can still be found out the exact same way. It makes no difference really, could you explain how it does?

If you have different IP's on seperate IP blocks how would they find out besides the server's hostname? I know that the provider I use has a random domain they use for the main hostname so it can not be "easily" found out. Know what I mean?

If you have different IP's on seperate IP blocks how would they find out besides the server's hostname? I know that the provider I use has a random domain they use for the main hostname so it can not be "easily" found out. Know what I mean?

What is the random domain? PM me, if you don't mind and I'll show you how it can be traced.

--Tina

What is the random domain? PM me, if you don't mind and I'll show you how it can be traced.

--Tina

PM sent Tina, thanks for showing me this - always wondered. Love learning new things! :)

So in conclusion, its makes no difference in finding out someone's a reseller even if you grant them there own private IPs for name servers. What we do is have private IPs for all name servers, which is better as its not wasting abunch of IPs.

Ex.

ns1.yourwebhosting.com > 00.000.000.01
ns2.yourwebhosting.com > 00.000.000.02

ns1.resellerwebhosting1.com > 00.000.000.03
ns2.resellerwebhosting1.com > 00.000.000.04

ns1.resellerwebhosting2.com > 00.000.000.03
ns2.resellerwebhosting2.com > 00.000.000.04

ns1.resellerwebhosting3.com > 00.000.000.03
ns2.resellerwebhosting3.com > 00.000.000.04

So it really would really be pointless to assign new IPs for new resellers, wouldn't it? Or have I missed something??

So in conclusion, its makes no difference in finding out someone's a reseller even if you grant them there own private IPs for name servers. What we do is have private IPs for all name servers, which is better as its not wasting abunch of IPs.

Ex.

ns1.yourwebhosting.com > 00.000.000.01
ns2.yourwebhosting.com > 00.000.000.02

ns1.resellerwebhosting1.com > 00.000.000.03
ns2.resellerwebhosting1.com > 00.000.000.04

ns1.resellerwebhosting2.com > 00.000.000.03
ns2.resellerwebhosting2.com > 00.000.000.04

ns1.resellerwebhosting3.com > 00.000.000.03
ns2.resellerwebhosting3.com > 00.000.000.04

So it really would really be pointless to assign new IPs for new resellers, wouldn't it? Or have I missed something??


You're forgetting one thing.
00.000.000.03 -> ??
00.000.000.04 -> ??

From what I remember certain mail servers need rDNS (reverse DNS) to accept mail (could be wrong..)

If you have ... say... 50 resellers pointing to these IP's but it rDNS resolves to yourdomain.com (ns1/2) then everyone knows where they host, etc. Plus it will somewhat show how many resellers you host (and how many you have on this server) through some online tools.

Hope I phrased it in a way that's easy to understand. If it's not let me know, and I'll re-phrase! :) Hope this helps bud.

You're forgetting one thing.
00.000.000.03 -> ??
00.000.000.04 -> ??

From what I remember certain mail servers need rDNS (reverse DNS) to accept mail (could be wrong..)

If you have ... say... 50 resellers pointing to these IP's but it rDNS resolves to yourdomain.com (ns1/2) then everyone knows where they host, etc. Plus it will somewhat show how many resellers you host (and how many you have on this server) through some online tools.

Hope I phrased it in a way that's easy to understand. If it's not let me know, and I'll re-phrase! :) Hope this helps bud.

Yeah I understand 100%, but either way people can find out your a reseller even if your assigned your OWN name server IPs.

Or am I wrong?

There's usually always a way. It just depends on how much effort people want to put forth to find out who's hosting you. Private IP's per reseller is a lot easier to protect their "privacy", especially if you change a few other settings on the server. It all depends on what the customer's want, you know?

Some people don't want their clients to know they're a reseller because it makes them look like a "starter company". Other's just don't care. It all depends on what the client wants :)

Hope I'm helping. :)

I have been providing shared IPs but allow them if they wish to use "Private Label" nameservers otherwise they have the generic ones we use which are anonymous

I am looking at revamping my resellers in some way

Del

I have 2 different nameserver packages,

1. free - shared IP
2. £4/m - dedicated Ip's, and have the IP's as hosting Ip's

If you offer "shared IPs" (where all your resellers use the same two IPs for their private nameservers), then it is simple to do a reverse lookup on the IP and see all the different nameservers that they are registered to.

In other words, you can see the nameservers for every reseller who is using those two IPs.

We give two new IPs to every reseller. There is minimal cost to do this, and it seems more "isolated", which is what most resellers want.

Hope that helps.

We also believe that providing 2 Dedicated IPs for each Reseller is a definite advantage -- for both the Hoster and Reseller. Couple that with being on an anonymously named Server, makes it very difficult for Reseller Clients to go around the Reseller; as in trying to reach the Hoster themselves for possibly better pricing for example.

With 2 Dedicated IPs, each Reseller can use one for their main Domain name, if they want or need an SSL Cert, and use the other one as a Shared IP for their Clients only. This can make big differences for the Server Admin, as far as record keeping and in seeing what is going on where.

You can do the following for reseller:

1) Register a new domain with private registration (keep registrar/billing info private)
2) Register 2 nameservers using the same domain and use the same 2 nameservers for your server as default nameservers with RDNS etc... to avoid mail bounce etc..
3) Assign the hostname to your server using the new domain
4) Make sure the new domain is using the same nameservers that you registered using the same domain.
5) Make sure your new domain does not points to your real site or just point it to coming soon page or some under construction page or make a small new site for reseller hosting.
6) Use shared nameserver hosting, i.e. use the same 2 ips even if the reseller wants his own nameservers, just ask your reseller to register his nameservers with the same ip that oyu used above to register your nameservers, this will save ips.

I hope it helps

Greets