Linux

Ask something
Discussion Locked

Finding the mole (part 2of 2, problem)

0 helpful
5 replies

by zk

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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.

5 replies

by mckaytech

I think the key is the statement "DNS is only specified on the proxy". Even with proxy, your client still needs to know where to find a DNS server so each client needs to have the address of a DNS server in its network settings. I suspect if you add the IP of a DNS server to the DHCP settings on the server and do an IPCONFIG release/renew at the workstation, you will be able to use the FQDN to reach your server.

paul

by zk

Hi Paul,

Problem solved.

DNS server doesn't need to be specified for every client. Proxy will do the name resolution for the client, because other sites work.

It was the TTL of the proxy's DNS server (which is ISP's). I was checking it onlytwo days after I change the zone for entry for the web server. And ISP DNS keep giving the proxy the old ip. It is all fine now. Appreciate it.

by zk

Thank you so much, Paul, for the help. I have raised the point for further suggestions.

That is one of my thoughts as well; the whole cause of the problem might be the client network.

The resolution is ok, as far as I can tell. Cause, it says,connecting server then the correct ip shows in the status bar, only then timed out on opening the page.

Every single site I know of work in the client network. Shouldn't proxy be successfully able to handle the name resolution for the client as well? Every client from the proxy network is able to see all other sites.

I was thinking it might also be something to do with Apache config. Particularly, cname and servername directives. I'm pretty new in Apache.

Please advise. Thanks.

This discussion is closed to new replies.