[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-users] RAQ2 - Still Can't send mail to AOL HELP!



On Wed, 23 Jan 2002, Paul Alcock wrote:

> > > There is no reverse configured
> > > It will resolve is you use raq1.agilitysystems.com
> > 
> > IIRC, that's the problem with sending to AOL. If you claim to be
> > raq1.agilitysystems.com [64.135.71.134] and a lookup of 64.135.71.134
> > doesn't resolve, AOL bounces the mail. They used to just $*itcan 
> > it with no
> > bounce, IIRC.
> Thanks Dan,
> but I'm not sending mail through raq1.agilitysystems.com ! :(
> (At least I don't think I am!) 
> It should be going through raq2.agilitysystems.com

Are you sure? they seem to be numbered in reverse for some reason...

raq1.agilitysystems.com.  22h47m11s IN A  64.135.71.134
raq2.agilitysystems.com.  23h58m9s  IN A  64.135.71.133

71.135.64.in-addr.arpa  nameserver = ns1.usda.net (Auth=1)
 134.71.135.64.in-addr.arpa

Server:  NS1.USDA.NET
Address:  64.135.0.60

Authoritative answers can be found from:
(root)  nameserver = J.ROOT-SERVERS.NET
[EG it's lame] That's why your reverse isn't working properly, something
is confused ..

Your machine knows what to reverse the IP to, but no-one has delegated
authority to it, so noone cares ;P

134.71.135.64.in-addr.arpa      name = raq1.agilitysystems.com
133.71.135.64.in-addr.arpa      name = raq2.agilitysystems.com

Interestingly, after pestering the usda.net nameservers for a bit, they
started answering for .133, but not for .134, hmm...flakiness...

gsh