Security Basics mailing list archives
Re: educating rDNS violators
From: Eric Brown <ericbrow () ziplip com>
Date: Mon, 23 Aug 2004 16:55:49 -0700 (PDT)
Hello all, I will admit, I thought I knew enough about DNS to get it working. I managed to send and recieve mail to myself from all the domains I managed. I could get to the right website. I ran into a domain that did exactly as Scott mentions here. The sysadmin for this domain was no help at all, and quite rude about it. It turned out it wasn't a problem with my DNS servers, but my upstream provider. They had to add a PTR entry to their DNS, so that all of our class C IP's mapped back to us. I'm certain that I don't know all I should about being a sysadmin. I do know I enjoy it a lot. I think this list is one of the best places to educate people like myself. That's my 2 cent anyway. Eric
-----Original Message----- From: SMiller () unimin com [mailto:SMiller () unimin com] Sent: Monday, August 23, 2004, 9:51 AM To: security-basics () securityfocus com Subject: educating rDNS violators Our mail administration group recently implemented blocking of all incoming messages from domains that cannot be resolved via reverseDNS, for purposes of spam prevention. Of course, there are quite a number of legitimate business contacts who do not have rDNS properly configured. Assuming that the rDNS criterion remains, the question becomes one of who will notify and/or educate the sender(s) about this issue. The only time-efficient way that I can think of to do this would be to have instructions and references in the body of the bounce message itself. Anyone tried that? Results? Other suggestions? Thanks in advance. Scott --------------------------------------------------------------------------- Computer Forensics Training at the InfoSec Institute. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse so that it never happens again. http://www.securityfocus.com/sponsor/InfoSecInstitute_security-basics_040817 ----------------------------------------------------------------------------
To do is to be. -Socrates To be is to do. -Satre Do be do be do. -Sinatra --------------------------------------------------------------------------- Computer Forensics Training at the InfoSec Institute. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse so that it never happens again. http://www.infosecinstitute.com/courses/computer_forensics_training.html ----------------------------------------------------------------------------
Current thread:
- Re: educating rDNS violators, (continued)
- Re: educating rDNS violators Derek Schaible (Aug 30)
- Re: educating rDNS violators JGrimshaw (Aug 24)
- Re: educating rDNS violators James Kelly (Aug 25)
- Re: educating rDNS violators Bryan S. Sampsel (Aug 25)
- Re: educating rDNS violators SMiller (Aug 26)
- Re: educating rDNS violators Derek Schaible (Aug 25)
- Re: educating rDNS violators Mark Reis (Aug 28)
- Re: educating rDNS violators Derek Schaible (Aug 30)
- Re: educating rDNS violators Bryan S. Sampsel (Aug 30)
- Re: educating rDNS violators James Kelly (Aug 25)
- Re: educating rDNS violators Chris Olave (Aug 24)
- Re: educating rDNS violators Eric Brown (Aug 24)
- RE: educating RDNS violators LordInfidel (Aug 26)