Adding IP...

[TMMM]

I'm a little confused on a couple of things here:
Currently my IP management looks like this here:
IP Status Reseller User(s) Nameserver Netmask Select
**.***.**.34 server 62 ns1.domain.com 255.255.255.248
**.**.**.35 free admin ns2.domain.com 255.255.255.248

Currently I have never used SSL and I would like to right now.

Since I have limited IP's, I plan to use jlasman's method of a system wide ssl cert for example:
https://secure.example.com/domain.name
Im a little concerned because ns2.domain.com is tied to that ip aswell, will this cause any conflicts? Will this not work since the .35 is the "server" ip?

I do have one more available IP that I can use outside of these two .34 and .35 that I have. Would it be best to insert a new nic card into the server and add the new ip in ip managment then assign that to the new domain? Or is this not neccessary?

Idealy I would like to use the *.35 if possible for the new domain and install a cert just for that domain.
Then If possible, I would like to use a new ip, say *.36 for the system wide cert.

Thank you for reading

I'm very new to SSL and managing ip's and dns with DA so please don't rag on me too bad =)

 

[nobaloney]

I'm a little confused on a couple of things here:
Currently my IP management looks like this here:
IP Status Reseller User(s) Nameserver Netmask Select
**.***.**.34 server 62 ns1.domain.com 255.255.255.248
**.**.**.35 free admin ns2.domain.com 255.255.255.248

Currently I have never used SSL and I would like to right now.

Since I have limited IP's, I plan to use jlasman's method of a system wide ssl cert for example:
https://secure.example.com/domain.name
Im a little concerned because ns2.domain.com is tied to that ip aswell, will this cause any conflicts? Will this not work since the .35 is the "server" ip?

.35 is not a server IP, at least not according to what you've included. It's a free IP# owned by admin. You can remove it from admin and attach it to any user you wish, and then set up the shared account.

You may have to remove ns2.domain.com from the IP# before you can change it, but that's not a problem.

Of course you can buy the cert from us and pay us only a few bucks to set it all up for you.

I do have one more available IP that I can use outside of these two .34 and .35 that I have. Would it be best to insert a new nic card into the server and add the new ip in ip managment then assign that to the new domain? Or is this not neccessary?

Not necessary. You can add the IP# through the same NIC you're already using for your two IP#s.

Idealy I would like to use the *.35 if possible for the new domain and install a cert just for that domain.
Then If possible, I would like to use a new ip, say *.36 for the system wide cert.

Now you've got me confused. What new domain? The one for the system-wide cert?

Jeff

 

[TMMM]

You may have to remove ns2.domain.com from the IP# before you can change it, but that's not a problem.

If I remove ns2.domain.com then the domains will show errors for only having one name server?

Of course you can buy the cert from us and pay us only a few bucks to set it all up for you.

Sounds good, what type of cert?

Not necessary. You can add the IP# through the same NIC you're already using for your two IP#s.

Would I want to add the additional ip on eth1 (*.35) as a "virtual interface"? As apposed to eth0(*.34 "system").

Now you've got me confused. What new domain? The one for the system-wide cert?

The "new domain" I'm referring to is the first domain on my server that is going to require its "own" ssl cert.

Given the fact that removing the *.35 from ns2 shouldnt be a problem. The best plan that I can think of is to have a system wide cert on the *.35 and then add a *.36 for the new domain who needs its own cert. Does that sound feasible?

At one point, and I can try this again tommorow; I took down eth1 (*.35) which seems to have only ties to ns2.domain.com and is a free ip in the DA ipmanagment, and when I took down that interface all of my websites were not visible. Does this seem logical? It seems that I need to look into this before I steal *.35 for a domain.

I appreciate your replying to my question.
Thank you
-Tom