Dotnetpanel Forums

I find this to be a big issue. My clients hope that when they get a dedicated IP that they can create multiple websites (Including subdomains) on their dedicated IP. However, when a website is created it takes up the IP by creating no Host Headers in IIS6. So when the client tries to create another website on his dedicated IP IIS6 wont allow it to operate since it's being used by another website. I think it's important that DNP create Host Headers for the domains when a client wants to put more than 1 website on a Dedicated IP.

Does anyone else find this to be an issue or is it just me? 

Yes - I found that really REALLY annoying as I have to then go in via RDP, and change this because when we try and add another domain even with wildcard entry, it doesn't actually add them to the host header, so the site never works properly.

I've found a few quirks with the control panel, and compared to HC7 which I also bought, it's not really as slick and 'easy to use', however, the appliction installer we use it for mainly to create websites using compiled and custom versions of DNN were not possible with HC7 as they build it into the appliction, so we run our DNN offerings manually and we're learning the quirks of the application as I think any product you buy will have.

A work around I found was to get the client to create a tempory domain using the master domain, which has a fixed IP and then manually assign via RDP, which isn't the best solution, but hey it's a work around which we've had to do from day one.

I understand their theory of it working, but in reality - it doesn't work as it should in my opinion, based on our requirements, but others might find it's not an issue at all.

Nina 

I also have this issue and I believe it's a major bug.

From the technical point of view, dedicated IP is for SSL only, but I believe this doesn't mean nobody is allowed to have dedicated IP for other purposes.

Resellers are keen to have their own dedicated IP for complete anonymity (RDNS for instance) but with the currect DNP version it is not possible.

I very much would like to see a patch for this issue.

Shojaee:

I also have this issue and I believe it's a major bug.

From the technical point of view, dedicated IP is for SSL only, but I believe this doesn't mean nobody is allowed to have dedicated IP for other purposes.

Resellers are keen to have their own dedicated IP for complete anonymity (RDNS for instance) but with the currect DNP version it is not possible.

I very much would like to see a patch for this issue.

It's not a bug, it's by design. And if you ask me, it's the correct design. You should only need 1 IP to host all websites, that's why it's called shared webhosting. The only valid reason for a dedicated IP is to run SSL, and in that case it will be the only domain running on that specific IP and that's why DNP doesn't add the host headers.

Giving resellers a dedicated IP doesn't garantuee their anonymity, it's just a small decoy, and if you ask me a bit pointless. That's why we also don't assign dedicated IPs for that reason, anyone can easily trackdown the true hoster, as they would still be using the DNS servers of the host. If one of our customers asks for white label they need to get a dedicated server and run their own name servers.

 There are clients who would like to put all their IP's on their dedicated IP. Trust me, I've had far more questions about why their sites aren't working on their dedicated IP than not. There must be a setting that allows host headers to be made so clients can put more than 1 site on their dedicated IP. I have yet to have one client say that this is a great idea only having the option to create one website on their dedicated IP... Clients get a dedicated IP so they can have hopes of putting several sites on that IP to separate from the other shared IP's with multiple customers. There are SEO reasons behind it.

Still, I really feel that the only valid reason for putting a website on a dedicated IP is to use SSL (or anonymous FTP) 

The reasons you give are no good:

- It's no use putting them on a dedicated IP to distuinguish them for from the other websites on that server. They would still be using the same name servers, thus not providing any white label. That would require a dedicated box with private name servers.

- SEO: It is true when customers link between their sites, Google gives a higher value to links that come from a different IP. But this is only the case when using IPs from different C classes.

So I would really consider making your customers clear that they are on shared hosting, which means they are paying a lower price then dedicated hosting but as a consequence are sharing certain stuff with other customers.

If customers would start asking root access to the server, would you also give it to them just because they want to? Bottomline, stop wasting your IPs

There should be an option for the client in the "websites" settings for their domain if they want to create Host Headers for that domain. Or when they choose to use the dedicated IP maybe there could be a check box to check if they want host headers to be made.

I have yet another client wanting to put more than 1 website on their dedicated IP. I guess I could do what you are doing and TELL THEM exactly what they can and can't do with the dedicated IP option...but I rather allow them to do as they please. If they want to put more than one website on a dedicated IP, then should be able to. I think this is an option that should be added.