Website not available internally Bade Daramola 11/17/2008 4:05:02 PM Hi, My company presently hosts her website and MX records internally ut we are having problems accessing that site from within the internal network. The website is accessible externally. We use the same domain name fmnplc.com within the internal network as well as our external website. What could be the problem and what must we do please somebody help me. Thanks. Bade -- MCP

Re: Website not available internally "Lanwench [MVP - Exchange]" <lanwench[ at ]heybuddy.donotsendme.unsolicitedmailatyahoo.com> 11/17/2008 4:43:29 PM Bade Daramola <BadeDaramola[ at ]discussions.microsoft.com> wrote: [Quoted Text] > Hi, > > My company presently hosts her website and MX records internally ut > we are having problems accessing that site from within the internal > network. The website is accessible externally. We use the same domain > name fmnplc.com within the internal network as well as our external > website. > > What could be the problem You've just described it - "We use the same domain name fmnplc.com within the internal network as well as our external website. " What that means is, when your internal users try to find www.whatever.com, your internal DNS server thinks itself responsible for *.whatever.com, and doesn't find www internally. > and what must we do please somebody help me. > > Thanks. > > Bade This is often called "split brain DNS" and isn't a big problem. Just create a host in your internal forward lookup zone for whatever.com, called www. Assign it the public IP address used by your external webhost.

Re: Website not available internally "Phillip Windell" <philwindell[ at ]hotmail.com> 11/17/2008 7:38:40 PM "Lanwench [MVP - Exchange]" <lanwench[ at ]heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message news:OGRFfONSJHA.3932[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] > This is often called "split brain DNS" and isn't a big problem. Just > create a host in your internal forward lookup zone for whatever.com, > called www. Assign it the public IP address used by your external webhost. You'd actually want the Internal IP#. You want to avoid making "u-turns" in the Firewall. Normal NAT Functionality will fail in many if not most firewall devices (which is probably the root of the problem already). I'm assuming that the "site" is actually on the LAN and is simply made available to the public through the firewall. But if it "lives" out on the internet with public IP# then yes you would use the public IP#. As always, the devil is in the deatilas :-) -- -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- Technet Library ISA2004 http://technet.microsoft.com/en-us/library/cc302436(TechNet.10).aspx ISA2006 http://technet.microsoft.com/en-us/library/bb898433(TechNet.10).aspx Understanding the ISA 2004 Access Rule Processing http://www.isaserver.org/articles/ISA2004_AccessRules.html Troubleshooting Client Authentication on Access Rules in ISA Server 2004 http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc Microsoft Internet Security & Acceleration Server: Partners http://www.microsoft.com/isaserver/partners/default.mspx Microsoft ISA Server Partners: Partner Hardware Solutions http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx -----------------------------------------------------

RE: Website not available internally James Yeomans BSc, MCSE 11/17/2008 10:36:03 PM create the www record on your intrernal zone because that server thinks its responsible for that domain and will therefore not forwsrd the queries any where else. James. -- James Yeomans, BSc, MCSE Ask me directly at: http://www.justaskjames.co.uk "Bade Daramola" wrote: [Quoted Text] > Hi, > > My company presently hosts her website and MX records internally ut we are > having problems accessing that site from within the internal network. The > website is accessible externally. We use the same domain name fmnplc.com > within the internal network as well as our external website. > > What could be the problem and what must we do please somebody help me. > > Thanks. > > Bade > -- > MCP

Re: Website not available internally "Lanwench [MVP - Exchange]" <lanwench[ at ]heybuddy.donotsendme.unsolicitedmailatyahoo.com> 11/18/2008 12:51:16 AM Phillip Windell <philwindell[ at ]hotmail.com> wrote: [Quoted Text] > "Lanwench [MVP - Exchange]" > <lanwench[ at ]heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in > message news:OGRFfONSJHA.3932[ at ]TK2MSFTNGP02.phx.gbl... >> This is often called "split brain DNS" and isn't a big problem. Just >> create a host in your internal forward lookup zone for whatever.com, >> called www. Assign it the public IP address used by your external >> webhost. > > You'd actually want the Internal IP#. You want to avoid making > "u-turns" in the Firewall. Normal NAT Functionality will fail in > many if not most firewall devices (which is probably the root of the > problem already). I'm assuming that the "site" is actually on the > LAN and is simply made available to the public through the firewall. > But if it "lives" out on the internet with public IP# then yes you > would use the public IP#. As always, the devil is in the deatilas :-) > -- Ach. I think I misread the original post. I thought he said he was hosting the website externally. If I'd read it properly (i.e., public DNS and website hosted on the LAN) I would instead have written "um...don't do that." However, if he wrote it accurately and that wasn't a typo, there should be no reason that the lookup should fail as is, honestly. There are just a slew of other potential problems! ;-)

Re: Website not available internally Paul Bergson [MVP-DS] <pbbergs[ at ]nospam_msn.com> 11/19/2008 1:23:05 PM Hello Bade, Define the dns records for your internal www server on your internal dns server, thereby avoiding it being passed to an external resolver. But leave the external dns definition alone, so external users can find your external www server. -- Paul Bergson MVP - Directory Services MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, 2003, 2000 (Early Achiever), NT4 http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. [Quoted Text] > Hi, > > My company presently hosts her website and MX records internally ut we > are having problems accessing that site from within the internal > network. The website is accessible externally. We use the same domain > name fmnplc.com within the internal network as well as our external > website. > > What could be the problem and what must we do please somebody help me. > > Thanks. > > Bade >