 |  |
Ross,
Re: New Version with NAT [correction]
From: Men & Mice Support
Date: Monday, May 14, 2001
Time: 9:02:20 pm
I believe that will work. However, note that I've never configured a
Cisco router/NAT server to do this, though I've answered questions
from customers with this type of setup. Just make sure to have your
DNS and web servers behind the Cisco box, relative to the outside
world, and make sure you have their DNS translation feature turned on.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
At 4:27 PM -0700 5/14/01, Ross Markbreiter wrote:
>We have
>3.Your NAT server is a Cisco firewall, and you have DNS translation
>turned on. In this case, you do everything with private IP addresses
>(including the load balance record), and the firewall takes care of
>the details.
>NAT is 10.1.1.1=38.x.x.x
>In the Cisco Router Access list
>Can we do that.
>
>___________________________________________________________________
>>At 6:54 PM -0700 5/11/01, Men & Mice Support wrote:
>>>At 4:43 PM -0700 5/11/01, Ross Markbreiter wrote:
>>>>Hi,
>>>>Last year I put in a request for Load balancing and fault tolerance
>>>>To work with NAT and Firewall, Just wondering if it was added to the
>>>>new version.
>>>
>>>No, I'm afraid not. While we have substantially changed the
>>>interface for load balance records (between 2.x and 3.x), we have
>>>not changed the essential mechanism.
>>
>>On further thought, that's not correct. We did make some minor
>>changes to the mechanism, and thus it is now possible to use a load
>>balance record for web servers behind a NAT server.
>>
>>There are some requirements to meet, though. In general (but not
>>always), this will mean that QuickDNS Server must be outside the
>>NAT server (possibly behind a different NAT server). Let me explain:
>>
>>- You must be able to connect to your name servers by their public
>>name, not by IP address.
>>
>>- QuickDNS Load Balancer (which must run on the same machine as
>>QuickDNS Server) must be able to contact the web servers by the
>>addresses used in the load balance record.
>>
>>I see three ways for this to work. They may be other possibilities.
>>
>>1. QuickDNS Server is outside the NAT server, possibly in a DMZ.
>>
>>2. Your NAT server is IPNetRouter from Sustainable Softworks, and
>>you have local NAT turned on. (I have yet to see this cool feature
>>on any other NAT server.) In this case, QuickDNS Server can also be
>>behind the NAT server, because it will be able to contact the web
>>servers by their public IP addresses. Also, with proper
>>configuration, you'll be able to connect Manager to Remote using a
>>server hostname that resolves to the public IP address of the
>>server.
>>
>>3. Your NAT server is a Cisco firewall, and you have DNS
>>translation turned on. In this case, you do everything with private
>>IP addresses (including the load balance record), and the firewall
>>takes care of the details.
>>____________________________________________________________________
>>Chris Buxton Men & Mice
>>cbuxton@menandmice.com We Make DNS Easy!
>
>Ross Markbreiter
>Director Sales
>The World Wide Web Store, Inc
>4349 Van Nuys Blvd.
>Sherman Oaks, Ca 91403
>http://www.worldwidewebstore.com
>Ph:818-905-6787
>Fax:818-905-6783
> Toll Free-888-999-7522
>ross@thewwwstore.com
Messages In This Thread:
Return to Digital Point Solutions' Home Page