[NCLUG] Pretty Pesky Port Passing Problem

John L. Bass jbass at dmsd.com
Mon Mar 24 11:02:47 MST 2003


Rich Young <rich at ExperiencePlus.Com> writes:

> We've recently installed a new web server on our network, inside the
> firewall, and simply port-passed :80 to the new server from the
> firewall/former webserver.  It works great if you're outside the building,
> but anyone inside the firewall can no longer simply type in the URL of our
> website and get it to load.  Using the internal IP address does work, but my
> co-workers would like to avoid memorizing any IP addresses....
>
> Does anyone have any advice on resolving this problem?

Consider using bind/named with sortlist?
Or different internal/external name servers?

John



More information about the NCLUG mailing list