Jorey Bump wrote:
> "Bergset" <sabergset@gmail.com> wrote in news:1128431351.134889.74430
> @g49g2000cwa.googlegroups.com:
>
>
> > Other config files on 192.168.1.1:
> >
> > "/etc/resolv.conf" contains:
> > search testdomain.com
> > nameserver 192.168.1.3
> > nameserver xxx.xxx.xxx.xxx (my ISP's DNS servers)
> > nameserver yyy.yyy.yyy.yyy
> >
> > "/etc/nsswitch.conf" contains:
> > hosts: files dns
> >
> > "/etc/hosts" contains (only non-IPv6 content):
> > 127.0.0.1 testserver localhost
> >
> > Doing "host test.testdomain.com" with this setup returns the correct IP
> > number (192.168.1.1). Doing "host 192.168.1.1" returns "testdomain.com"
> > which is what i expected.
> > Restarting Apache results in "Cannot resolve host name
> > test.testdomain.com -- Ignoring!" errors in my syslog for all my
> > VirtualHosts.
>
> Just a guess, but is it possible that you are running apache in a chroot
> environment and it chokes when attempting to read /etc/hosts?

No, it is a vanilla Debian 3.1 installation. Apache resolves correct
when I put my virtualhosts in /etc/hosts so theres no problem there.

--
Svein Arild Bergset