|
|
 |  |
Re: binding 2 IPs to a name serverFrom: Men & Mice Support Date: Monday, September 18, 2000
Time: 12:44:38 pmAt 3:21 PM -0400 9/18/00, Karl Schroll wrote:
>We are switching T1 carriers which will require changing info at the root
>server and readdressing our name server to a new IP number. Is it possible
>for Open Transport to respond to two IP addresses, so that during the time
>it takes for the root change to filter out across the net, our name server
>will respond to the old IP number and the new IP number? If so, do I need
>to add a second ethernet port to the Mac and if so, can someone suggest one
>that they know works? Thanks a lot in advance. Please keep it simple, I
>know just enough to be dangerous. :)
This reminds me of the children's game Fortunately/Unfortunately.
Unfortunately:
Mac OS computers don't natively support multiple network interfaces.
Such support can be added with software such as IPNetRouter (from
Sustainable Softworks) or several of Vicomsoft's gateway/proxy
products.
Fortunately:
The Mac OS can, however, be configured to answer on multiple IP
addresses using its built-in Ethernet port. There should be a sample
IP Secondary Addresses file in your preferences folder. (Requires Mac
OS 8.1 or later.)
Unfortunately:
QuickDNS Pro Server does not directly support multiple IP addresses.
Support for the extra addresses configured in IP Secondary Addresses
must be added by server software developers, and we haven't done that
yet. (New version coming soon...)
Fortunately:
Mac OS 9's version of Open Transport does some internal routing
tricks to force QuickDNS Pro Server to listen on multiple IP
addresses. (Also works on some versions of 8.6.)
Unfortunately:
The routing tricks that Open Transport uses can cause problems for a
small percentage (much less than 1%) of your potential visitors. I
won't bore you with the details; suffice to say that the affected
potential visitors won't be able to contact your DNS servers if you
set things up this way.
Fortunately:
The people thus affected also have had trouble (at various times in
the past) with www.apple.com, www.microsoft.com, and several others,
due to the exact same problem. The problem is due to a poor design of
a proxy or NAT server (at the visitor's end of things) - it makes
more assumptions than are strictly necessary. There are very few such
devices still in operation.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
|

Return to Digital Point Solutions' Home Page |