IP Gateway and DNS resolution

[Jim Mapes]

Our BMgr 3.0 / NW5 server was running DHCP and DNS as well. We're
moving the DHCP and DNS functions to NT. The DHCP migration is
complete, DHCP unloaded from NW5, running on NT. DNS is running on
NT. Waited a few days for DHCP leases to refresh so DHCP clients
would get a DNS server IP address for the NT DNS server. BM/NW5
server resolve.cfg has been changed to point to NS1=NT DNS server,
NS2&3 = our ISP DNS servers. NAMED was unloaded on BM server.

Life was good. Until clients running IP Gateway service started
getting our internal web servers resolved as public IP addresses and
thus, unable to browse to them. Clntrust/NAT clients are OK. We use
DNS only to resolve internal web url's to the private IP address, then
it forwards to our ISP's DNS.

I've reloaded NAMED on BM server, seems to be working again for IP
Gateway users. I see resolutions still being done on the Named
console screen. I don't understand why these resolutions are still
being done when resolve.cfg points to the NT DNS server. Have I
missed something? With Named down, shouldn't BM use the NT DNS
server, which is properly resolving internal url's for non-IP Gateway
users?
Thanks,
Jim