Recently I was contacted by my provider. They got a complain from another provider that a host with an IPv4 address I’m using was part of a DDOS attack. The mail from the other provider looked liked automatically generated and even contained a hint how to check the IP:
dig www.google.com @IP
I checked as soon as I could. Yes the Server the IP belongs to runs a resolver. But: The resolver listens only to IPv6 and has an access list for the IPv6 prefix I’m using. Of course the check via dig failed. I looked deeper into the problem and I think I found out how my resolver become part of the DDOS.
Yes I’m guilty. Guilty of reading some blogs and running a web based RSS reader on my server. And the RSS reader is just doing it’s job: Getting RSS feeds. In order to do this it has to do DNS lookups several times a day. The provider that complained hosts several blogs I read and so their DNS server got several request over the day. And that triggers the DDOS detection appliance which send out an automated mail. Would have been nice if it would follow it’s own advice using dig to check if the alleged open DNS resolver is really open.
I think about writing an invoice for an hour of troubleshooting.