 |  |
At 12:22 PM -0500 4/29/01, Jim Grisham wrote:
Re: QDNS on multihomed IPs
From: Men & Mice Support
Date: Sunday, April 29, 2001
Time: 6:28:03 pm
>At 10:09 AM -0700 on 4/29/01, you wrote:
>>On 04/29/2001 10:04 AM, The Defendant "Jim Grisham"
>><jgrisham@dailyillini.com> Confessed:
>>
>>> At 1:25 AM -0700 on 4/28/01, you wrote:
>>>> At 3:55 AM +0100 4/28/01, Steve Linford wrote:
>>>>> I just discovered that QDNS 3 doesn't answer on multihomed IPs but
>>>>> only on the machine's main IP (in the TCP/IP panel).
>>>>
>>>> That is correct. QuickDNS Server 3.5 for Mac OS 8/9 will still have
>>>> this limitation.
>>>>
>>>> If, after 3.5 is released in a few days, you change server platforms
>>>> to Mac OS X or any of our other supported server platforms, you
>>>> won't have this problem.
>>>
>>> I'm confused. One IP address in the TCP/IP control panel, one or more
>>> in the IP Secondary Addresses file, right? Single-link multihoming?
>>>
>>> It worked for me using 2.x, and it works for me now using 3.0. The
>>> main IP is on our internal lan 192.168.0/24 private subnet and the
>>> secondary address is the world-accessible one. I have Keyserver from
>>> Sassafras running on the same machine, and that multi-homes fine as
>>> well.
>>>
>>> Jim
>>
>>Quick DNS will not work reliably on the secondary
>>IP
Actually, in a few cases, it will. This may be one of them - the
secondary address is not on the same subnet, and only one of the two
addresses leads to the Internet. Therefore, Open Transport's routing
engine may behave properly.
Understand, what makes QuickDNS Pro Server respond on multiple
addresses isn't QuickDNS Pro Server itself. It doesn't understand
multiple addresses at all. However, recent versions of Open Transport
(starting somewhere around Mac OS 8.6) include something similar to a
NAT server for such software - it's not a very good NAT server, in
that it doesn't remember on which interface an incoming request
arrived, but it therefore doesn't take much RAM.
>>I would switch it and make the pub. Ip the main, if you are running a public
>>nameserver.
>>
>
>Is there any way to test this?
Yes, using the Unix command-line tool 'dig', a tool for sending DNS
queries. It's intolerant of the problem that's often caused by using
QuickDNS Pro on a secondary address.
We have a web interface to dig available here:
<http://us.mirror.menandmice.com/cgi-bin/DoDig>
Your server responds just fine to queries sent by dig.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
Messages In This Thread:
Return to Digital Point Solutions' Home Page