hosts file

[Derek Ragona]

Well, your resolv.conf points to 192.168.1.1, what is at that address?  Do 
you have any other DNS issues?

Can you ping localhost, or 127.0.0.1?

Is named running?

         -Derek


At 02:14 PM 3/15/2006, eoghan wrote:
>Derek Ragona wrote:
>>Sorry, my mistake.  Check:
>>/etc/nsswitch.conf
>>You should the line:
>>hosts: files dns
>>With the files listed first
>>         -Derek
>
>Hi
>yes that is in my nsswitch.conf:
>hosts: files dns
>any other ideas?
>
>>At 01:56 PM 3/15/2006, eoghan wrote:
>>>Derek Ragona wrote:
>>>>Check your resolv.conf, should have files first.
>>>>         -Derek
>>>
>>>resolve.conf reads
>>>nameserver 192.168.1.1
>>>
>>>
>>>>At 01:44 PM 3/15/2006, eoghan wrote:
>>>>>Steve Bertrand wrote:
>>>>>>>Yes, mine reads:
>>>>>>>::1             localhost nathaniel
>>>>>>>127.0.0.1       localhost nathaniel
>>>>>>>Upon starting apache, i can only get to it by using the ip.
>>>>>>>127.0.0.1 wont work either. I just get the unable to connect message 
>>>>>>>from the browser. Any ideas?
>>>>>>Under the Listen directive in your httpd.conf file, are you binding
>>>>>>Apache to a single IP?
>>>>>>Mine reads:
>>>>>>Listen 80
>>>>>>Which means listen on port 80 on all IP's. If you have an entry as such:
>>>>>>Listen 123.456.789.111:80
>>>>>>It will listen on port 80 on ONLY that IP, and ignore all other
>>>>>>requests, including localhost/127.0.0.1.
>>>>>>Regards,
>>>>>>Steve
>>>>>
>>>>>Hi
>>>>>Yep, its:
>>>>>Listen 80
>>>>>and
>>>>>ServerName localhost
>>>>>Where do i get the text from the boot? Im getting some weird Network 
>>>>>is unreachable messages in here that may have something to do with it?
>>>>>Eoghan
>