Date: Thu, 22 Sep 2005 15:47:19 -0600 From: Steve Suhre <tech@nano.net> To: Steve Suhre <tech@nano.net> Cc: freebsd-hackers@freebsd.org Subject: Re: BGP & reverse dns Message-ID: <43332667.2030906@nano.net> In-Reply-To: <20050922184632.GA16321@lava.net> References: <20050922120047.825E016A429@hub.freebsd.org> <20050922184632.GA16321@lava.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks, I think they figured it out. The customer is always right....sigh.... I used the list because I needed to know if there was a quick fix here, I added them to a spamassassin whitelist. Clifton Royston wrote: >On Thu, Sep 22, 2005 at 12:00:47PM +0000, freebsd-hackers-request@freebsd.org wrote: > > >>Date: Wed, 21 Sep 2005 09:51:49 -0600 >>From: Steve Suhre <tech@nano.net> >>Subject: BGP & reverse dns >>To: freebsd-hackers@freebsd.org >>Message-ID: <43318195.8000304@nano.net> >>Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >>I have a client who's using BGP on their own network but use our mail >>servers. They're having trouble sending mail because the server here >>can't resolve the IP address back to their network. And if I run the IP >>through DNSStuff.com it returns an infinite loop error. They claim they >>aren't having trouble anywhere else though.... >> >>I don't want to turn off reverse lookups, is there anyway to get around >>this? Or a simple fix on their end? I know nothing about BGP routing... >>We're running sendmail, and spammassassin through procmail. The mail >>problem started recently when we upgraded sendmail and added >>spamassassin, but their DNS/BGP problems have been there for a while.... >> >> > > This question belongs on a different list; I'd normally say >freebsd-questions, but it has nothing to do with FreeBSD at all as far >as I can see. Try inet-access or some similar mailing list which deals >with Internet access and configuration issues. > > To save a little list bandwidth and give you a starting point for >that list, my tip is forget about BGP unless it's proved that there is >a routing problem. The routing protocol your client is running (BGP) >has nothing to do with DNS; these operate on completely different >network layers. Useful tools for resolving DNS problems are "dig", >"host", and "whois"; these will let you tell what name server is >responsible and whether there is a problem with their name servers. > > The immediate question to look into would be who delegated their >address space to them, and what name server is responsible for its >rDNS. > -- Clifton > > > -- Steve Suhre tech@nano.net 719.439.6052 Cell 719.632.2897 Home
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43332667.2030906>