From: Matthew Galgoci <mgalgoci@redhat.com>
To: overseers@sources.redhat.com
Cc: cgf@redhat.com
Subject: [msw@redhat.com: [rao@gnu.org: Reverse DNS on gcc.gnu.org broken]]
Date: Mon, 06 Jan 2003 15:51:00 -0000 [thread overview]
Message-ID: <20030106105026.D19237@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]
Hi Folks,
I checked this myself, recursing from the a.root-servers.net machine,
and indeed, the authoratative name servers for the 209.249.29. netblock
are not responding with a forward dns entry for 209.249.29.67
I realize that this is a bit of a quandry since sources.redhat.com
responds for multiple domains, but surely the reverse dns should
resolve to _something_, right?
Let me know if I need to take further action on this.
Kind regards,
Matthew Galgoci
----- Forwarded message from Mark Klein via RT <sysadmin@gnu.org> -----
Envelope-to: rao@gnu.org
Delivery-date: Sat, 04 Jan 2003 21:43:12 -0500
Subject: [gnu.org #15993] Reverse DNS on gcc.gnu.org
From: "Mark Klein via RT" <sysadmin@gnu.org>
Reply-To: sysadmin@gnu.org
X-RT-Loop-Prevention: gnu.org
RT-Ticket: gnu.org #15993
Managed-by: RT 2.0.14 (http://bestpractical.com/rt/)
RT-Originator: mklein@dis.com
Bcc:
To Whom it May Concern:
Sometime around the second or third week of December, reverse lookups
on gcc.gnu.org started failing and continues to this point:
dig -x 209.249.29.67
; <<>> DiG 9.2.1 <<>> -x 209.249.29.67
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 42271
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;67.29.249.209.in-addr.arpa. IN PTR
;; Query time: 107 msec
;; SERVER: 64.7.69.254#53(64.7.69.254)
;; WHEN: Sat Jan 4 18:35:33 2003
;; MSG SIZE rcvd: 44
As part of our spam blocking strategy, we have sendmail configured to
reject mail from sites where reverse DNS does not provide a valid
address. As a result, our email subscriptions to some of the gnu
lists did not get through until we temporarily disabled this.
Do you plan to make this a permanent "feature" or was it just an
oversite? Our needing to disable that checking in sendmail has meant
that our spam receipts have tripled.
Regards,
M.
--
Mark Klein
http://www.dis.com
PGP Key Available
--
Matthew Galgoci "Dirty deeds, done dirt cheap"
System Administrator
Red Hat, Inc
919.754.3700 x44155
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2003-01-06 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 15:51 Matthew Galgoci [this message]
2003-01-06 17:02 ` Christopher Faylor
2003-01-16 10:34 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030106105026.D19237@redhat.com \
--to=mgalgoci@redhat.com \
--cc=cgf@redhat.com \
--cc=overseers@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).