Hi,

I'm testing a DNS setup that mainly is used in connection with a
virtualhost'ed Apache 1.3.33 server. As this is part of a bind learning
process for me, it might be that my problem is more suited for a bind
group... but anyway:

The problem is that the Apache server can't resolve any of my name
based virtualhosts during startup. The strange thing is that doing DNS
lookup manually with dig, nslookup or whatever is no problem at all.
Both normal and reverse lookup produces correct results.

The first nameserver statement in /etc/resolv.conf points to the test
nameserver. I assume Apache's resolve method uses this information.

Putting the virtualhost domains in the hosts file produces no errors,
so it's safe to assume that this is a network DNS issue.

My bind setup is using wildcard as follows:
@ IN A 192.168.1.1
* IN CNAME @

The zone is "testdomain.com" and the virtualhost domains are mostly
subdomain of "testdomain.com".

I know CNAME wildcards is somewhat dubious, but this isn't an issue
that would cause the Apache resolve problem. A setup without wildcard
produce the same error.
The DNS and Apache servers are on separate hosts at 192.168.1.0/24.

Does anyone have an idea about the cause of this Apache resolve
problem?

My system(s):
Debian 3.1 Sarge (Apache 1.3.33, Bind 9.2.4)

-
Svein Arild Bergset