Separate DNS Server for private and public IPs

Hello. I would like to configure Windows XP to use one DNS server for
private IPs and a separate DNS server for public IPs. Can someone please
point me to helpful information?

Lee

Lee C. <nomail@spam.com> wrote:
> Hello. I would like to configure Windows XP to use one DNS server for
> private IPs and a separate DNS server for public IPs. Can someone
> please point me to helpful information?
>
> Lee

There's no way to do that. Your workstation is going to use the primary DNS
server and if that fails or isn't available will try the secondary (and
won't retry the primary right away). What you can do is set up the private
DNS server with forwarders to public/Internet DNS servers so your clients
can use a single DNS server to handle all requests.

I appreciate your trying to help; but, I don't believe you. I have a couple
ideas on how to achieve it; but, none that I'm excited to try (for various
reasons). I don't want to contaminate anyone's mind with my ideas just yet;
so, I'm still waiting for someone to offer a solution. I don't know does not
equal it's impossible.

, Lee

"Lanwench [MVP - Exchange]" wrote:

> There's no way to do that. Your workstation is going to use the primary DNS
> server and if that fails or isn't available will try the secondary (and
> won't retry the primary right away). What you can do is set up the private
> DNS server with forwarders to public/Internet DNS servers so your clients
> can use a single DNS server to handle all requests.

Lee <Lee@discussions.microsoft.com> wrote:
> I appreciate your trying to help; but, I don't believe you. I have a
> couple ideas on how to achieve it; but, none that I'm excited to try
> (for various reasons). I don't want to contaminate anyone's mind
> with my ideas just yet; so, I'm still waiting for someone to offer a
> solution. I don't know does not equal it's impossible.

OK - have fun storming the castle!
>
> , Lee
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> There's no way to do that. Your workstation is going to use the
>> primary DNS server and if that fails or isn't available will try the
>> secondary (and won't retry the primary right away). What you can do
>> is set up the private DNS server with forwarders to public/Internet
>> DNS servers so your clients can use a single DNS server to handle
>> all requests.

I take it you want the name of -for example a mailserver- to resolve to its
private IPs internally, and to the Internet IP when outside the premises?

In this case, setup an internal DNS server, and create a zone for your
internal domain, with A-records pointing to the private IPs of computers, and
associated PTRs. As the internal DNS server does not have a SoA for the
domain, it will be ignored by other DNS servers. Thus, this zone will not be
seen by internet computers, only by your internal ones.

Other DNS requests should be forwarded to your ISP's DNS server, or to the
root servers.

Laptops using DHCP should then be able to access the server(s)
transparently, internally and externally.

A simpler (though less robust) way to achieve this is to refer to the server
by its hostname only, and set a DNS suffix in the Advanced TCP/IP settings.
Thus, if the host can be resolved directly when on the LAN it will be, if not
then a fully-qualified name will be tried, and this will succeed when
outside.

"Lee C." wrote:

> Hello. I would like to configure Windows XP to use one DNS server for
> private IPs and a separate DNS server for public IPs. Can someone please
> point me to helpful information?
>
> Lee
>
>
>

"Lee C." <nomail@spam.com> wrote in
news:eKgf0N0AJHA.2264@TK2MSFTNGP02.phx.gbl:

> Hello. I would like to configure Windows XP to use one DNS server
> for private IPs and a separate DNS server for public IPs. Can
> someone please point me to helpful information?
>

Depending on what you're really trying to do, you can use a private DNS
locally and configure a proxy server for internet access. The proxy
server will use a public DNS for requests sent its way.

-- John