Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 Aug 2002 22:35:11 -0700 (PDT)
From:      Edwin Groothuis <edwin@topaz.mdcc.cx>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   misc/42278: mx1.freebsd.org has problems talking to ns1/ns2.secondary.com
Message-ID:  <200209010535.g815ZBia034250@www.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         42278
>Category:       misc
>Synopsis:       mx1.freebsd.org has problems talking to ns1/ns2.secondary.com
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Aug 31 22:40:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Edwin Groothuis
>Release:        n/a
>Organization:
-
>Environment:
n/a
>Description:
Since saturday august 31th 2002, 13:45 EST (UTC+10) I'm not able to send
any more mail to and haven't received any more mail FreeBSD.org domains.

After some searching I found out that mx1.freebsd.org refuses all mail
from domains hosted on secondary.com:

Host topaz.mdcc.cx: mail from @mavetju.org:
    host mx1.freebsd.org[216.136.204.125] said: 450 <edwin@mavetju.org>: Sender
address rejected: Domain not found)

Host bps.jodocus.org.
    450 <bps.jodocus.org>: Helo command rejected: Host not found

Host mud.fataldimensions.org.
    450 <mud.fataldimensions.org>: Helo command rejected: Host not found

These are three different machines all over the world with one thing in
common: their DNS services are provided by secondary.com.

This can be because of a couple of things:

- mx1.freebsd.org doesn't know where ns1/ns2.secondary.com are.
- ns1/ns2.secondary.com don't know where mx1.freebsd.org is.
- somebody is blocking IP traffic somewhere between freebsd.org and
  secondary.com
- ns1/ns2.secondary.com are blocking DNS requests coming from mx1.freebsd.org

Which one? I don't know.


I had earlier today send an email to postmaster/hostmaster@freebsd.org 
and got an answer from Peter Wemm, who gave me this information:

mx1> traceroute 198.133.199.4
traceroute to 198.133.199.4 (198.133.199.4), 64 hops max, 40 byte packets
 1  bas2-m.freebsd.sc5.yahoo.com (216.136.204.5)  0.337 ms  0.197 ms  0.184 ms
 2  ge-1-0-0.msr2.sc5.yahoo.com (216.115.100.145)  0.231 ms  0.231 ms  0.226 ms
 3  ge-2-1-0.pat1.pao.yahoo.com (216.115.101.229)  0.758 ms  0.789 ms  0.740 ms
 4  paix.nominum.com (198.32.176.120)  1.912 ms  2.281 ms  2.023 ms
 5  paix.nominum.com (198.32.176.120)  2.349 ms !X *  1.754 ms !X

mx1> dig mavetju.org. ns @198.133.199.3 +vc

; <<>> DiG 8.3 <<>> mavetju.org. ns @198.133.199.3 +vc
; (1 server found)
;; res options: init usevc recurs defnam dnsrch
;; res_nsend to server 198.133.199.3  198.133.199.3: Operation timed out
mx1>

>How-To-Repeat:
On mx1.freebsd.org, "dig mavetju.org. ns @198.133.199.3 +vc"


>Fix:
Right now this PR is only to keep track of the problem, I've filed a PR with secondary.com too and am waiting for their answers.

>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209010535.g815ZBia034250>