becuse your are using them for nameservers they are still avail for shared & dedicated useHow come when I assign people 2 IPs for name servers, and they register them, the IPs are still shown as availiable as being used as DEDICATED IPs
Why would you mention the box though? I said nothing about sharing name servers.jayh38 said:Its not that I or anyone else is NOT getting it, You do not acknowlege that the box is not checked anywhere from what I have read.
I know how to do that but I want it so it does that by its self.jayh38 said:I dont think you fully read the posts which is difficult to help you.
I would suggest looking at the cPanel WHM manual but to answer your
WHM > IP Functions > Show/Edit Reserved Ip's
Basicly your saying the same things, I know all of this as if I didn't, why would I make this kind of post in the first place. Point is they STILL come up, I would have to make them a reserved IP in order to stop this. I wanted to know if there was a way to make it so I wouldn't have to do so. I don't know how much more clear I can possibly get now.jayh38 said:Ok Now I understand how you are thinking this through. I was trying to explain
this through several posts that you can share nameserver IP addresses that belong
to no dedicated domain. For example...
Main share IP 333.333.333.333
Lets say your host name is host.example.com. You have your name servers setup and your server is running fine and all is good. Now you just got a client requesting their own personal name servers for a WHM. Excellent, so lets do this,
First you need to add their A records into their dns zone:
A record entry for myclient.com.
ns1 in A 184.108.40.206
ns2 in A 220.127.116.11
Next modify their registrar.
Tell them they need to create their private name server in their registrar with the
You do not have to waste IP addresses on client name servers in order
to use your present NS IP addresses. As long as you do not assign your name server IP's to a domain, you will get the message that "there is no website configured at this address" no matter how many personal name servers you create and assign to those addresses.
Just simply add the A record to your clients dns zone.
If your nameserver IP's do resolve to a website then the name server IP is using the share IP and the first zone configured in httpd.conf will be resolved as if it were a dedicated IP. So you will need to be sure that your main share IP is not using a ns IP
You can then edit your clients WHM, reseller center and have them use their private name servers by default. Also edit zone templates so new accounts are assigned the proper
information for their own clients.
I hope this all makes sense after all these posts.
Seems that other guy knew what I was talking about. I don't see how you don't get it. I've explained it in so many ways, and made it as simple as it can be.jayh38 said:I'm sure he knows that as well.
good luck with this thread, what you know and what you say are not matching
|Thread starter||Similar threads||Forum||Replies||Date|
|R||Odd Issue, possibly permit related.||General Discussion||5|
|B||httpd.conf odd entries||General Discussion||3|
|O||Odd issue with new installs||General Discussion||3|
|S||odd restore issue||General Discussion||1|
|M||Sub-domain, add-on domain oddities||General Discussion||2|