IPCop 2 & DNS

I have a RED + ORANGE + BLUE + GREEN IPCop v2.0.0 set up.
8 public IP addresses, with aliases set correctly.
2 servers in DMZ: 1 is Primary DNS + WEB + MAIL, 2 is Secondary DNS + MAIL,
both exposed to outside world.

I host a few domains on these DNS servers (yes - I know - DNS primary &
secondary should be at different locations, but this is mainly for
development purposes).

I use hostnames and a single primary domain name for all my servers, for
example:

  fw.mydomain.com is the IPCop firewall pc.
  ns1.mydomain.com is first server.
  ns2.mydomain.com is second server.

ns1 hosts the zone record for mydomain.com (with secondary on ns2) and has
all the correct A records, etc. including a "A" record for www.mydomain.com.

DNS is set up correctly AFAIK, online tests say OK, and everything worked
fine with IPCop v1.4.21 - Computers in GREEN and BLUE could resolve DNS
addresses OK for mydomain.com, e.g. a pc in GREEN could browse
www.mydomain.com ok.

But with IPCop v2.0.0, it seems that machines in GREEN cannot resolve any
address for mydomain.com, except for fw.mydomain.com, e.g. now when I open a
browser to www.mydomain.com, it displays a "page not found" error.

It seems that if I add a hosts record in the IPCop GUI for www, it then
becomes browse-able.

Can anyone explain why in more detail?
How do I configure IPCop to use the zone record for mydomain.com hosted on
ns1, so that I don't have to add multiple hostname entries via the web GUI?

Thanks,

John Campbell



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct