2 "work arounds" I have used in the past are:

- have an internal dns server which has an entry for www.mydomain.com to the internal IP address
- have a static mapping in your hosts file

>
>So youre on the inside of a NAT interface, trying to talk directly to the
>outside of your NAT interface?
>
>It doesn't work.
>
>Its also well documented...
>
>Simply put...
>
>www.mydomain.com resolves to xxx.xxx.xxx.xxx in the DNS.
>
>Because you're NAT'd, internally you hold ip yyy.yyy.yyy.yyy and your
>connections to the internet are translated so that you appear to be on ip
>xxx.xxx.xxx.xxx to the rest of the world.
>
>When you do a DNS lookup on www.mydomain.com you're getting the answer
>xxx.xxx.xxx.xxx. When you try to talk to that IP, your router realises
>that its an IP bound to the router (not the webserver).
>
>The pinhole rules are rules that apply to inbound traffic coming from the
>external interface - not the internal one. Internally you'd actually need
>to be bouncing the connection in-then-out the _same_ interface. Doesn't
>work that way.
>
>If you want to test your webserver you'll need to hit up a web proxy of
>some sort - try anonymizer.com.
>Or use a local DNS resolver which provides your internal IP, not your
>external one, when browsing the host involved. (hosts file.)
>
>Mark.
>
>
>
>

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message