Problem:
(The following are all tested from a truly remote network)
I used IE 5.0 on a NT workstation that is directly connected to the Internet
(no proxy) and I can use both ip and FQDN (ie, www.mydomain.com) to access
the web page. They are fine (showed up). I also tried using dialup POTS as
well. Again both ip and FQDN works.
Now the fun part is when I use a client behind MS Proxy 2.0 SP1 (NT4.0 SP6a)
, it says opening page and then timed out when using FQDN. But, accessing by
ip is ok. So seems like name res problem. This MS Proxy is also DHCP Server.
I tried using web proxy only, wsp only, and both on the client. Still no go
with FQDN. So, I added the ip in host file, then using web proxy, bypass the
address (specified do not use proxy for thesein IE). Then suddenly the FQDN
access works. BTW this LAN doesn’t have internal DNS. DNS is only specified
on the Proxy. The LAT and others (filters, clients) are all setup correctly.
So, the question is, is it the problem on the server network, on the client
network, or the DNS, the MS Proxy? The url in question is
http://www.zealousminds.com The ip right now is 65.26.44.51. And chances are
if you’re behind MS Proxy, it won’t work with name. Only with ip. But, all
other types of firewall (or dialup) and you should see the page.
Apache configtest seems to be ok.
I would be happy to provide my config files, zone files, if it would
help any, as this is only a test network.