Cannot view own www site

[resoremix]

I know there have been other posts covering the old split DNS problem of not being able to view your own publicly accessible site but I took the route of calling my internal network company.local and letting my ISP be authoritative for the company.co.uk domain to avoid any such issues.

However, now that my DMZ webserver is finally online at

http://www.company.co.uk,

it can only be accessed from outside the network. Machines on the internal network simply receive a "cannot be contacted browser error". A 'ping

http://www.company.co.uk'

command from such a machine successfully resolves and pings the correct public IP address for the site.

I hope it is not a DNS problem and I'm pretty sure it isn't as my ISP hosts the company.co.uk domain and simply forwards all requests to a public IP it supplied us with. The only DNS we run is the internal Active Directory requirement for company.local. All unresolved DNS lookups are forwarded to our ISP's DNS servers.

I suspect the problem is firewall (Watchguard Firebox 700) related. There is no problem accessing any external web sites from within company.local so do I need to be aware of any blocking that could be taking place between the trusted network and the DMZ?

Any other ideas?

Thanks very much for your thoughts.

 

[darranagl]

I presume you have a proxy setting in your desktop web browser.

Open IE and click Tools, Internet Options, Connections tab then LAN Settings. Tick the 'Bypass proxy server for local addresses', click the Advanced button and put your web site in the 'Do not use proxy server for addresses starting with' box (eg

http://www.company.co.uk).

Click OK etc.

This will let the browser go directly to your web server on the DMZ bypassing the proxy server with keeps sending the request out onto the Internet for it to get lost (source and destination addresses are the same so the request is not returned).
New Zealand, a great place to visit.

http://www.southland.org.nz

 

[resoremix]

Thanks very much for the reply darranagl.

What you say makes perfect sense but I need to enter the IP address and port of the proxy server. I am not sure what this should be as I do not have a dedicated proxy server as such. My Watchguard Firebox has three interfaces (so 3 IP addresses): Internal, Optional (DMZ) and External and runs an HTTP proxy service but does not expose a dedicated IP address for it.

Any further ideas?

 

[darranagl]

Do you have your browser set to "Automatically Detect Settings"?

Can you put the IP address of your Web Server into your browser and see the web page? If so try using a HOSTS (Win9x) or LMHOSTS (NT/Win2k/XP) file to over-ride the name resolution of your site.
New Zealand, a great place to visit.

http://www.southland.org.nz

 

[GlenJohnson]

Type ipconfig /all from a dos box on your server and look for anything strange. Also try a route print and see what comes up. Hosts and LMHOSTS files per darranagl is a great idea also. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"We will either find a way, or make one".
Hannibal (247-183 B.C.); Carthaginian general.

 

[experienced]

I had the same problem, but in my case I did make the mistake of naming our domain as our web domain. So, I am not sure if my solution to our problem (suggested by someone in this forum earlier) would would work for you, but nobody so far mentioned it, so why don't you try it anyway?

I went to Start-->Programs-->Administrative Tools-->DNS. There, I opened Forward Lookup Zones and selected a zone I already created. Went to "Action" at the menu bar and chose "New Host..." You would be asked to enter 2 things, a domain name and an IP address. I entered our web domain name and its IP address. Clicked on "Add Host." This took care of our problem.

 

[resoremix]

Thanks for the help again people.

darranagl: Using the IP of the site from my browser gives the same results. I do not have "Automatically Detect Settings" selected although I tried this to no avail.

Glen: Everything looks OK on the ipconfig front.

I think I'll try and get some help from Watchguard on this as I suspect its an overkeen firewall issue.

 

[tom11011]

It's probably the firewall/router trying to route out it's own address.

Can you make a dns entry to your internal lan?