On Thu, 24 Sep 2009, Stan Hoeppner wrote: > Is this a problem with uribl.com's MX setup in DNS, or a problem on my > end? Or both? My DNS provider enables wildcard DNS for my domain. I'm > not sure if that is part of this problem, but seems possible. If so, > what can I do, short of switching DNS providers, to prevent this hard > bounce from happening, and enable proper roll over to the other MX'en > listed upon failure to the primary?
uribl.com's DNS appears to be fine as of right now. > Sep 22 19:34:14 greer postfix/smtp[11384]: connect to > mx.uribl.com[63.216.184.130]: No route to host (port 25) > Sep 22 19:34:14 greer postfix/smtp[11384]: 87D543DA160: > to=<redac...@uribl.com>, relay=mx[65.41.216.221]:25, delay=1.4, Huh? Why is the nexthop for f...@uribl.com your own Postfix instance? > delays=0.09/0.03/1.3/0, dsn=5.4.6, status=bounced (mail for uribl.com > loops back to myself) > > 65.41.216.221 is the public IP behind which my Postfix server sits (PAT) > and for which my DNS provider enables wildcard. > > ;; ANSWER SECTION: > uribl.com. 43200 IN MX 10 mx. Huh? > uribl.com. 43200 IN MX 10 mx.uribl.com. OK. > uribl.com. 43200 IN MX 100 mx2. Huh? > uribl.com. 43200 IN MX 100 mx2.uribl.com. OK. FWIW: % dig +short MX uribl.com 10 mx.uribl.com. 10 mx2.uribl.com. -- Sahil Tandon <sa...@tandon.net>
