Let me just first point out what DNS servers we have:

#1. Microsoft DNS server in our corporate office (been in production for years)
#2. NetWare DNS server in our corporate office, clustered (in
pre-deployment stage now... will replace our Microsoft DNS server)
#3. NetWare DNS server in our remote satellite office, standalone (running
for 1 year now)


When I boot up my Windows workstation configured to DNS Server #2, I
immediately ping a DNS name which has both a record on our internal DNS
server and a record on public DNS out on the internet. It resolves to the
public ip address for that DNS name. If I then do ipconfig /flushdns and
then ipconfig /registerdns, and then ping again, it resolves correctly to
the internal IP address.

If I boot up my Windows workstation configured to DNS Server #1, I ping the
same DNS name and it immediately resolves to our private IP address.

If I boot up my windows workstation to DNS Server #3 (keeping in mind this
is across a WAN point-to-point link), pinging that DNS name also
immediately resolves to our private IP address.

So I'm assuming, back to the first scenario, that somehow when Windows
first boots up, it thinks my DNS server is unavailable and switches to the
Alternate DNS address configured on my machine which is the one given by
our ISP. Perhaps the DNS server isn't responding quickly enough because it
is on a cluster?

Funny thing is, this problem does NOT exist on my Macintosh workstation.
Only occurs on Windows machines.

Otherwise, once I flush and re-register on my Windows machine, everything
runs FLAWLESSLY.

Any ideas?
Bryen