Setting Up DNS Entry for Multiple Network Segments

On a machine that acts as a firewall or a router, where there are many
network segments with separate IP networks defined, are you expected to fill
in the same value for the DNS server on all of the separate networks? Or
should you define the DNS server on just one network and then leave DNS
Server blank for all other networks?

I can't imagine too many cases when I would want one machine to use
different namespaces simultaneously. I assume that for most cases you
want a single computer to have a single DNS server. I'm confused why
Microsoft doesn't just provide for a single default entry across all
interfaces.

--
Will

I think you are asking about a multihomed DNS client machine and whether you
need to supply the same primary DNS server for each adapter. The answer is
NO. Windows will query the first DNS server assigned to the preferred
adapter - top of the Local Area Connection binding order. If a negative
response is received, no further query is attempted. If no response is
received, then Windows will attempt to query the DNS server (if any)
configured for another adapter - but if this is the same DNS server, well
.............

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Will" <westes-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On a machine that acts as a firewall or a router, where there are many
> network segments with separate IP networks defined, are you expected to
fill
> in the same value for the DNS server on all of the separate networks? Or
> should you define the DNS server on just one network and then leave DNS
> Server blank for all other networks?
>
> I can't imagine too many cases when I would want one machine to use
> different namespaces simultaneously. I assume that for most cases you
> want a single computer to have a single DNS server. I'm confused why
> Microsoft doesn't just provide for a single default entry across all
> interfaces.
>
> --
> Will
>
>