I got around this issue by creating a zone and www record in my internal DNS 
for the webserver/website

So while your external DNS server may be setup to resolve
www.somesite.com<http://www.somesite.com>-->
66.22.13.2 <http://66.22.13.2>
m0n0wall has NAT 1:1 setup for 66.22.13.2 <http://66.22.13.2> ---> 
192.168.0.5 <http://192.168.0.5>
Your internal DNS has a zone for www.somesite.com
<http://www.somesite.com>with a www record for
192.168.0.5 <http://192.168.0.5>

When anyone on the LAN tupes the URL www.somesite.com<http://www.somesite.com>, 
they are really going to 192.168.0.5 <http://192.168.0.5>

- Don


On 9/9/05, James McKeand <james at mckeand dot biz> wrote:
> 
> Cimino Vittorio wrote:
> > Lan ----------- m0n0Wall ----------- Router ----------- Internet
> > |
> > WebServer ------+
> >
> > m0n0wall from external 80 to webserver 80 (Nat Incoming)
> >
> > When i try to access external:80 from an internal (Lan) machine the
> > connection is refused. Any other ip (any other internet address) try
> > to access to natted webserver all is okay !!!
> >
> > An Help ? Tnx !
> 
> Classic LAN-NAT see:
> 
> http://www.m0n0.ch/wall/docbook/faq-lannat.html
> 
> _________________________________
> James W. McKeand
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> 
>