Re: internal DNS (windows server) conflict with external DNS (ISP) - f

From: Steve Bruce, mct (nospam_at_msn.com)
Date: 09/16/04 

Date: Thu, 16 Sep 2004 18:30:02 -0500

While opinions vary on the wisdom of this, it sounds like you must be using
the same domain name inside and out ??

The failover interval between querying the first or second dns server listed
in dns properties is almost instantaneous. It's purpose isn't for
sequencing, but to find a DNS server that holds a zone. If two servers hold
a zone of the same name, it is likely that they will send queries to both
available dns servers listed.

An alternative configuration to try, would be to remove the ISP's dns server
listing on the clients. Create static A records on you internal dns server
for your external servers that are supposed to be accessed with a public IP
by internal users.

Then configure forwarders on your dns server pointing the ISP's DNS Servers.

"randyv" <randyv@discussions.microsoft.com> wrote in message
news:BD29D783-F825-497B-9A0B-A987DDE73ADF@microsoft.com...
> I'm having a frustrating problem.
>
> I have an internal DNS set up on our Windows2000 Advanced Server. This
> DNS
> resolves our server names to their internal IPs for folks at the corporate
> office. That's all it really does, there are no forwarders, nor is it
> really
> 'public' - not publishing/syncing 'internal' IPs for our server names with
> other DNS servers.
> We have an external DNS that resolves our server names to their external
> IP
> addresses - the DNS service is supplied by our ISP.
>
> Corporate users for the most part are using WindowsXP Pro. Their TCP/IP
> properties are set to use an internal DHCP server to get their IP address
> (this runs behind our corporate firewall). The DNS servers however are
> set
> - one (internal DNS) is primary and alternate is our ISP's external DNS.
>
> The idea here was that these corporate clients would always resolve at the
> primary first - hence all our server names would get the proper (internal)
> IP
> for the users
> at corporate, and all external names (like www.google.com) would resolve
> at
> the alternate (external) DNS server at our ISP. External (branch) users
> would always resolve the server names with their external IP addresses
> using
> the external DNS provided by our ISP.
>
> PROBLEM DESCRIPTION -
> What happens is that when a corporat user's WindowsXP Pro client reboots,
> for some reason, the company server names try to resolve to the external
> name
> server (alternate not primary DNS), which resolves to an external IP
> address.
> Since our firewall keeps the corporate users from 'going out and coming
> back
> in', this resolution fails - mail cannot pop, web pages cannot load.
>
> It is easy for me to fix, I can shut down the DNS server and client
> service
> and restart it, or I can do an ipconfig /release and ipconfig /renew - why
> that works I cannot figure out DHCP has nothing to do with name resolving,
> I
> just figure it is forcing the client to recognize the internal DNS server
> somehow.
>
> However, while it is easy for me, it is constantly happening all over
> corporate, which is irritating, and giving IT unwanted exposure in the
> executive office.
>
> Does anyone have an idea why the WindowsXP Pro client is not resolving
> names
> 'hierarchically'? That is, why isn't the client trying to resolve the
> name
> first at the primary, and only if not found at the primary, resolving to
> the
> alternate?
>
> Any advice is appreciated !!!
>
>
> --
> randyv

Relevant Pages

  • Re: static dns and computer accounts
    ... client don't should be to join to domain. ... I need require that the ip of a computer can resolve (reverse o ... dns server to add a machine account to domain ... this client have correct ip of the DNS Server in TCP/IP ...
    (microsoft.public.windows.server.active_directory)
  • Re: limit bandwidth consumption by user
    ... third time it would resolve. ... This happens both on an XP Client and on the ... SBS server itself. ... All clients use the SBS DNS Server which forwards ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant join win2003 as member server in domain 2003
    ... I tried to join a client which its OS is Win2k3,but I faced an error ... using an ISP's DNS server in TCPIP properties. ... Keep in mind you cannot mix ISP and internal DNS either. ... Instead of the website you're using, I suggest to use OEx (Outlook Express ...
    (microsoft.public.windows.server.networking)
  • Re: RWW Issue
    ... can resolve this issue: ... | I remote desktop into it. ... | desktop is enabled to allow remote connections. ... | DNS server failed the update request. ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID: 5504
    ... > localhost entry in forward lookup. ... > generated by a client, it is coming from the internal ... > it sends four queries to each root hint server to resolve ... DNS server would try to resolve a name unless it is asked to resolve it. ...
    (microsoft.public.win2000.dns)
Loading