httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: [BUG]: "DNS problems with virtual domains" on BSDI (fwd)
Date Wed, 12 Feb 1997 03:23:57 GMT
Ensure that 206.31.149.192 has a reverse ip map (try "dig -x
206.31.149.192" or "nslookup 206.31.149.192" on the command line).

If you cannot add a reverse ip map for it then specify a ServerName and
that will avoid the necessity for the server to actually do the reverse
lookup.  (I recommend you do this anyhow, otherwise your server can't boot
without working DNS.) 

Dean

On Wed, 12 Feb 1997, Rob Hartill wrote:

> 
> Acked.
> 
> If you think you know the answer, please respond to the submitter.
> 
> ---------- Forwarded message ----------
> Date: Tue Feb 11 17:28:15 1997
> From: mgrommet@insolwwb.net
> To: apache-bugs%apache.org@organic.com
> Subject: [BUG]: "DNS problems with virtual domains" on BSDI
> 
> Submitter: mgrommet@insolwwb.net
> Operating system: BSDI, version: 2.1
> Version of Apache Used: 1.2b6
> Extra Modules used: 
> URL exhibiting problem: 
> 
> Symptoms:
> --
> When I attempt to run httpd,
> it gives me a cannot
> resolve hostname for 206.31.149.192 (Check DNS)
> 
> I have been attempting to upgrade
> our web server from version 1.0
> (which works perfectly)  
> DNS is (at least for 1.0) correct.
> 
> The IP # is always the last domain listed
> in the virtual domains
> 
> --
> 
> Backtrace:
> --
> 
> --
> 
> 
> 


Mime
View raw message