Strange DNS Query ...

Is there such a case that a client machine make a DNS query to a machine
which is not in the list of the client's pre-configured DNS server?

In details: I have an AD server with 2 interfaces (call it if-A and if-B),
if-A serves DHCP and DNS, if-B serves DHCP requests for a different network.
I have a Ethereal trace which shows that a client machine queries the AD
server's if-B which is not one of the client's pre-configured DNS servers.
But if-A is one of the pre-configured DNS servers for this client.

I would appreciate if you could think of any reasons for such a "out of the
blue" DNS query ...

Thanks in Advance!
Polaris

You can ask additionally on
microsoft.public.windowsnt.protocol.tcpip

Arkady

"Polaris" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is there such a case that a client machine make a DNS query to a machine
> which is not in the list of the client's pre-configured DNS server?
>
> In details: I have an AD server with 2 interfaces (call it if-A and if-B),
> if-A serves DHCP and DNS, if-B serves DHCP requests for a different
> network. I have a Ethereal trace which shows that a client machine queries
> the AD server's if-B which is not one of the client's pre-configured DNS
> servers. But if-A is one of the pre-configured DNS servers for this
> client.
>
> I would appreciate if you could think of any reasons for such a "out of
> the blue" DNS query ...
>
> Thanks in Advance!
> Polaris
>