[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.58.0402130142380.848@rubycon.man.szczecin.pl>
From: cadence at aci.com.pl (Tomasz Grabowski)
Subject: Partial protection against MyDoom
Hello.
I have not been able to find simmilar information on the Internet, so I'm
posting it here. Maybe someone will find it as a solution to MyDoom
e-mails flood. But if it is already known, sorry for wasting your time.
* * *
It looks that MyDoom is not using the MX flag of particular domain. Look
at the following example:
$ host -t ANY domain.example.com
[snip]
7200 ;retry refresh this often
3600000 ;expiration period
172800 ;minimum TTL
)
domain.example.com mail is handled (pri=0) by mail.domain.example.com
This is a common example of configuration of 'big' domain. You can see
that MX for this domain is mail.domain.example.com.
There is in fact no such host like domain.example.com. If you will try to
lookup for such configured domain directly, you will end up with the
"domain.example.com: Non-existent host".
If you have simmilar situation and you are still suffering from enormous
amount of MyDoom e-mails, you can configure your domain like this:
$ host -t ANY domain.example.com
[snip]
7200 ;retry refresh this often
3600000 ;expiration period
172800 ;minimum TTL
)
domain.example.com has address 127.0.0.1
domain.example.com mail is handled (pri=0) by mail.domain.example.com
It should not affect your domain (real SMTP servers will use MX flag and
send e-mails to mail.domain.example.com) but MyDoom will be using this
127.0.0.1 address instead, thus your domain will be protected.
Opinions are welcome.
Regards,
--
Tomasz Grabowski
Technical University of Szczecin, +48 (91)4494234
Academic Centre of Computer Science www.man.szczecin.pl
Powered by blists - more mailing lists