Search Again:

Re: PTR records and reverse zone authority

From: Erich Kaminsky
Date: Tuesday, August 10, 1999
Time: 9:37:00 pm

Actually I seem to have worked this all out by simply removing resolution
to any of the secondary ip numbers. I am using a Netopia Router and OT's
Secondary IP Address File to assign multiple IP's to the same machine.
Until I got your most recent post I was not aware that Quick DNS Pro could
not recognize anything but the primary IP number. I am using QDNS v 2.1

As soon as I made 206.117.128.36 my primary IP and resolved DNS, Web, and
Mail to that same number everything began to hum like a sewing machine.

Thanks for all of your help.



>>I wouldn't be surprised at all if I've configured something incorrectly.
>>
>>The names and adresses are as follows:
>>
>>mail.usconnect.com ............. 206.117.128.35
>>ns1.usconnect.com .............. 206.117.128.36
>>ns2.usconnect.com .............. 206.117.128.46
>>virtual web resolves to ....... 206.117.128.34
>>
>>Everything except ns2.usconnect.com .... 206.117.128.46 is on the same
>>machine.
>
>So you're using multiple IP addresses on your main server? What method are
>you using to do this (OT's IP Secondary Addresses file, IPNetRouter, or one
>of Vicomsoft's products)?
>
>I ask because the current shipping version of QuickDNS Pro doesn't have
>support for multiple addresses. However, it is obviously working with your
>current setup.
>
>Actually, according to your DNS, all of the above names except ns2 resolve
>to 206.117.128.36.
>
>>Local smtp testing shows no problems finding the mail server but mail that
>>bounces back looks like so:
>
>I've had DNS Expert run a thorough analysis of usconnect.com. It turned up
>a few interesting errors, but nothing that explains why mail would bounce.
>
>What version of QuickDNS Pro are you using? I ask because both your servers
>failed the spoofing test.
>
>[snip]
>
>> ----- Transcript of session follows -----
>>451 <ek@usconnect.com>... usconnect.com: Name server timeout
>
>This line indicates that the problem lies somewhere in the domain name
>system. However, there's nothing wrong with your zone file that I can see.
>
>There is no indication in the delay notification as to why the DNS lookup
>failed, though I just queried the server in question; it was able to show
>me your MX record and the address of mail.usconnect.com.
>
>In other words, I can't see any reason for the problem, unless it was
>caused by a transient network failure.
>____________________________________________________________________
>Chris Buxton Men & Mice
>cbuxton@menandmice.com http://www.menandmice.com
Erich Kaminsky
K2 Consulting, Inc.
ek@k-2.net



Messages In This Thread:



Return to Digital Point Solutions' Home Page