resolving locally
From: Paddy (patrick_at_scotcomms.co.uk)
Date: 01/30/04
- Next message: Horst Knobloch: "Re: nat works with ppp but not eth0"
- Previous message: Cameron Kerr: "Re: Route Question"
- Next in thread: Cameron Kerr: "Re: resolving locally"
- Reply: Cameron Kerr: "Re: resolving locally"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 30 Jan 2004 11:14:03 -0000
Hi,
We have apache running a SSL site and a few name based virtual sites. This
server sits in our DMZ. All names on the server resolve to private IPs via
hosts. The firewall maps public IPs to private IPs. All is working well
until now. We now need to do curl from one of the virtual sites to the
secure site. For some reason Apache is resolving the name to the Public IP
and the Firewall is stopping this from happening.
If (on the local machine) I ping the name of any of the sites I get a
response from the correct private IP. If I telnet the same name it tries to
connect to the public IP.
Why would ping return the IP from the hosts file yet Apache, Lynx and telnet
resolve to the public IP. I noticed in host.conf that multi was set to on, I
set this to off but it didn't help. In hosts.conf the order is hosts bind.
What am I missing?
TIA,
Patrick
- Next message: Horst Knobloch: "Re: nat works with ppp but not eth0"
- Previous message: Cameron Kerr: "Re: Route Question"
- Next in thread: Cameron Kerr: "Re: resolving locally"
- Reply: Cameron Kerr: "Re: resolving locally"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
