Re: BGP & reverse dns

From: Steve Suhre (tech_at_nano.net)
Date: 09/22/05

  • Next message: Doug Barton: "Fixing an error condition for 'rm -P'"
    Date: Thu, 22 Sep 2005 15:47:19 -0600
    To: Steve Suhre <tech@nano.net>
    
    

    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
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
    

  • Next message: Doug Barton: "Fixing an error condition for 'rm -P'"

    Relevant Pages

    • Re: Bad NTP servers jeopardizing the pool.ntp.orginitiative
      ... I had problems with these servers in past. ... looks like BGP ... routing issue. ... Network engineer ...
      (comp.protocols.time.ntp)
    • Re: 2.6.12.2 dies after 24 hours
      ... >> so we take the few percent performance hit for something that doesn't ... > Interesting - When I got the problem it was on mail servers under high ... some patches to try and fix it for both reiserfs and ext3, ... > prepare_writeallocates space, starts a transaction ...
      (Linux-Kernel)
    • Re: POP3 E-mail Issue After Swing Migration
      ... only be using POP3 and SMTP servers under corporate control. ... changing it in the ISA Server Management Console, Server, Configuration, ... how in the heck do I fix this?! ...
      (microsoft.public.windows.server.sbs)
    • RE: Truncated message
      ... I was going to do the same fix this weekend. ... > This is becoming annoying as it is happening on all of our servers. ... > click OK to shutdown the system and reboot into Directory Services Restore ... > ended up having to rebuild the server. ...
      (microsoft.public.win2000.active_directory)
    • Re: Loooonnnngggg time to log in...Need advice
      ... This is the first time i've had this particular ... from looking at the logs on the two servers having ... then I know how to fix it. ... >Hi Jason, ...
      (RedHat)