Re: ISA 2000 - can't browse FQDN

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: A.Klimkin (aklimkin)
Date: 02/14/05 

Date: Mon, 14 Feb 2005 09:55:27 +0300

You have got two options here:
Either clear the DNS property from private interface or from the public.
I recommend to not have the public interface configured with external DNS
server address. In this case you should configure forwarders on your
internal DNS server to pass requests that it cannot hadle to the external
DNS server. Take a read DNS server help to find out how to do this. Also
make sure that your internal ISA interface is listed first in the adapters
bindings order (My Network Places->Properties->Advanced->Advanced Settings).
If you configure your ISA server like this, you should be successful with
previous recommendations about hitting your external web server.
There is some additional reading for you:
http://www.isaserver.org/tutorials/Understanding_how_ISA_server_clients_use_DNS.html
http://www.isaserver.org/tutorials/DNS_for_ISA_Server.html

Regards,
Andrew

"Paul Roddy" <proddy@noemail.com.com> wrote in message
news:Ow5XNhjEFHA.2876@TK2MSFTNGP12.phx.gbl...
> Hi Andrew,
>
> "A.Klimkin" <aklimkin at mail dot ru> wrote in message
> news:uSqukoPEFHA.3536@TK2MSFTNGP15.phx.gbl...
>>I want to ask your to provide some additional information.
>> 1. What is your ISA server interfaces configuration? Namely, how do their
>> DNS server property configured?
>
> I have 2 interfaces, one public, one private. The private interface uses
> the ISP's DNS server and the private interface uses the internal DNS
> server which is the same as the ISA server
>
>> 2. What type of clients do you use? I mean snat, web proxy or firewall
>> clients? And how do their DNS server property configured?
>
> I'm using Windows XP clients and MS IE v6.0 - IE is configured to use port
> 8080 on the ISA server to access the Internet. I am not using any other
> client or winsock client with these work stations.
>
>> Different ISA clients resolves FQDNs different ways. Depending on the
>> client type and DNS server address it configured with you might be
>> successful or not with your issue.
>
>

Relevant Pages

  • Re: Netlogon service problem
    ... loopback interface, it doesn't always work properly and can cause issues. ... Is there a problem here because the DC also has a NIC with a different IP address with the loopback as its DNS server. ... Netlogon will attempt to, and succeed,> reregister later. ...
    (microsoft.public.win2000.active_directory)
  • Re: Should DCs with DNS point to self first?
    ... If you've problems then that's another situation, but the poster is asking for where should the DNS pointing to ... No. There's no reason to use other DNS server when you have all locally, by doing so IMO you're wasting server resources and network traffic just for fun ... It depends entirely on the configuration and DESIRES of the administrators. ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Configuration
    ... SRV3 also a Primary DNS server for ... I am not able to understand the configuration of DNS server did by ... xyz.abc.com has two domain controller and both has Primary Zone for ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... I have looked at most of the articles you sited and I have configured DNS ... The DNS server lists only itself as the preferred server with no ... Best practices for DNS client settings in Windows 2000 Server and in Windows ... -Exchange configuration. ...
    (microsoft.public.windows.server.dns)
  • Re: setting up and configuring dns server on my windows 2000 box
    ... >don't we start with a brief description of your DNS ... Windows 2000 IP Configuration ... >where the DNS server is physically joined to). ... I just cannot seem to get things to resolve ...
    (microsoft.public.win2000.dns)