|
|
 |  |
Re: reverse? headachesFrom: Karl Schroll Date: Wednesday, November 29, 2000
Time: 9:16:14 amThanks Aaron.
Karl
--
> From: Aaron Lynch <a.list@ninewire.com>
> Reply-To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Date: Wed, 29 Nov 2000 08:43:34 -0800
> To: quick dns list <quickdns-talk@lists.menandmice.com>
> Subject: Re: reverse? headaches
>
> Well, they are probably trying to do a reverse lookup of 207.224.73.11.
> When I do, us west's nameservers fail to answer. So there is a problem
> there. Looks to me like maybe you don't have authority of the IP block, or
> if you do, US West has other issues with the setup.
>
> I'd mail the postmaster of geocities, because this is almost certainly
> against RFC. And as such, they may be prepared for it as a FAQ to allow
> your server if you tell them who you are and explian that it's not spam.
>
>
>
>
>
> On 11/29/00 7:46 AM, The Defendant "Karl Schroll"
> <schroll@digitalfrontier.com> Confessed:
>
>> We use QDNS, EIMS and ListStar. We host several lists that send out
>> thousands of emails a day (ski reports).
>>
>> For all mail that is being sent to the geocities.com domain from ListStar
>> via EIMS, the mail is bounced back to me with the following:
>>
>> The following message could not be delivered to Mackwb2pcv@geocities.com at
>> host geocities.com (209.1.224.29) because the sender address was rejected.
>> 550 <wp3inch@ns2.digitalfrontier.com>... unresolvable host name - sorry,you
>> are 207.224.73.11
>>
>> This only happens for geocities.com. All of our other mail service is
>> working correctly.
>>
>> 207.224.73.11 is EIMS, mail.digitalfrontier.com. ns2.digitalfrontier.com
>> runs liststar and secondary QDNS and is at 207.224.73.13.
>>
>> In QDNS, for the digitalfrontier.com record, we have an entry for
>> ns2.digitalfrontier.com with type "A", pointing to 207.224.73.13.
>>
>> I used QDNS domain assistant to set up all of our reverse domains. It
>> created a reverse record with, among other things, an entry of
>>
>> 11.73.224.207.in-addr.arpa. of type "PTR" pointing to
>> mail.digitalfrontier.com
>>
>> and
>>
>> 13.73.224.207.in-addr.arpa of type "PTR" pointing to
>> ns2.digitalfrontier.com.
>>
>> Can anyone offer advice on why mail to geocites.com (only) is failing?
>> Thanks!
>>
>>
>
|

Return to Digital Point Solutions' Home Page |