Re: [LUG] Re: Apache DNS an resolving both externally and internally

["Kevin Tunison" <ktunison@xxxxxxxxx>]

 Thank you - it has been a good read on ip aliasing.

 

I did solve the problem. It ended up being the internal DNS that I had set up wrong.  I had to add another domain, then add a CNAME record in the internal domain to the newly added external domain.  On top of that, the box I was testing with had an external secondary DNS configured, so even when the *right* settings went on (all other clients resolved fine), I was none the wiser.  My lesson learned on why to not use external dns as a secondary!

 

With regards to the ip aliasing, the tldp mentions that it is a bad idea to run an external AND internal on the same NIC because of the amount of collissions.  Is that still valid with giga-ether I wonder.

 

 

On 3/9/06, Simon Waters <simon@xxxxxxxxxxxxxx > wrote:

Hi Kevin,

I think the point being missed is each HTTPS site needs a separate IP
address (or IP address, port, combination, but it is easier to use IP
address).

We have servers at work with multiple HTTPS sites, and multiple virtual
hosts, and it can get quite confusing as to how Apache is configured.

Listen 80
Listen 443
NameVirtualHost a.b.c.d :80

Then the "virtualhost" statement in each site should explicitly state
the IP address and port being used by each site.

I'm guessing you've enabled "NameVirtualHost" on the IP address you have
the HTTPS site on, which will just confuse things.

You can just alias an extra IP on the webserver, stick all the HTTPS
stuff on that, and keep it separate. Probably have to do some port
forwarding on the firewall if you only have one public IP address to
play with.

--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html