HELP! Change to exclusive IP to enable an SSL certificate causing nameserver problems

I am using a dedicated Linux server with Plesk Control Panel through GoDaddy.  I am trying to enable my first SSL certificate which requres an exclusive IP address.  I am running a nameserver on the dedicated Linux machine and (I think) am running into nameserver problems with the new IP address.  Here is the layout:

ns1.domain.com.   A   Shared-IP-Address-1
ns2.domain.com.   A   Shared-IP-Address-1

TYPICAL DOMAIN SETUP THAT WORKS RIGHT NOW FOR SHARED IP:
domain2.com.   A   Shared-IP-Address-1
domain2.com.   NS   ns1.domain.com.
domain2.com.   NS   ns2.domain.com.

THIS DNS SETUP DOESN'T WORK FOR EXCLUSIVE IP:
domain3.com.   A   Exclusive-IP-Address-2
domain3.com.   NS   ns1.domain.com.
domain3.com.   NS   ns2.domain.com.


Every domain hosted on the shared IP (Shared-IP-Address-1) has been working great.  Will my nameserver only point to domains on the shared IP since it is pointing to that IP only?
LVL 2
matt1237Asked:
Who is Participating?
 
matt1237Connect With a Mentor Author Commented:
You guys are really sharp in mentioning things like... what's wrong here?
Something very humbling happened.  DNS propigated :(  Since I am running my own nameserver, I was under the false assumtion that changes I make on my nameserver would be seen almost instantly across the webscape.  I now realize, after a long discussion with a DNS guru friend of mine, that I am (surprise) restricted to the same propigation issies as every other nameserver.
The one thing that I can do to see my server changes instantly (at least locally on my desktop) is to make my nameserver a resolving nameserver and use it as the primary nameserver for my local desktop.  This will ensure that I don't have to wait for my ISP to update the cache on their DNS server(s) before I see results made on my GoDaddy server.
0
 
matt1237Author Commented:
Even a partial answer would help me!
0
 
ahoffmannConnect With a Mentor Commented:
hmm, don't realy understand what you mean/what's your problem ...

Anyway, if I assume that you want to have different FQDN on the same IP and each with its own SSL cert, that's not possible with apache (not sure for other web servers, but I doubt)
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
RowleyConnect With a Mentor Commented:
I don't really get what you're trying to convey either, but if its any help you can have an SSL enabled virtual host reside on the same address as a namevirtualhost. i.e:

SSL IP Virtual Host:
www.monkeys.com --> 1.2.3.4

Name Virtual Host:
www.badgers.com --> 1.2.3.4
www.chipmunks.com --> 1.2.3.4
www.squirrels.com --> 1.2.3.4


You're only ever going to be able to serve ssl for a single common name without warnings, unless you get a wildcard cert.
0
 
ahoffmannConnect With a Mentor Commented:
apache's name-based virtual host can only serve *one* SSL enabled virtual host, that has nothing to do with the cert
0
 
RowleyConnect With a Mentor Commented:
Agreed. I did specify the SSL portion would be on an IP virtual host.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.