At 02:44 PM 1/18/02 -0500, Mike Burger wrote: >Now, however, the systems behind the firewall can't access the sites on the >server...ie, workstation at 192.168.0.3 can't access any of the sites hosted >on 192.168.0.1, because the DNS entries for those sites point them back >outside the firewall...it would seem that, while the outside world can get . . . >Any ideas?
Simple: Two DNS servers (or Bind-9 with dual-view DNS if you're feeling masochistic). Setup a DNS server for/on your LAN (referenced in your dhcpd.conf and on any statically configured clients) which considers itself a master for your domain, and returns the private IP's of your servers (and does caching DNS for everything else). Then configure a second DNS server (i.e. the one you've got now) to respond to DNS queries from outside your firewall with the public address(es). If you don't actually do your own DNS for clients outside your LAN then just configure an internal DNS server that thinks it's a master for your domain etc. (as above) and let people outside your LAN use whatever DNS service your domain is really served by. -- Who is this General Failure, and why is he reading my hard disk? _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
