eMule Accessing DNS Port

[Wings_of_Azrael]

In my firewall log, it says that eMule (some guy from Finland on DSL) has tried to access my port 53 from remote port 4672. I know 4672 is a legitimate port for eMule to send traffic through. However, I have a rule to allow traffic through my ISP's DNS server... and right below it I have a rule to block all other traffic through port 53. What does it mean that eMule is trying to access my port 53? Is this usual activity?

Need help. Me scared, but me also want downloadie on eMule.

[zaphodiv]

Presumably this is UDP.

>me scared
This is not a reason to be scared, you should not have a service
listening on port 53 UDP so sending a packet to that port would
do nothing even if your firewall did not catch it.

[Wings_of_Azrael]

Ok, now I'm getting attempts by eMule to access ports 21 (FTP) and port 80 (HTTP). The point is not really so much that I'm worried about getting hacked. It's more about wanting to know why this is occuring and for what purpose does eMule need to access these ports. Is it some anti-piracy organization, different methods of searching the ed2k network, or what? Also, I'd like to know in case opening such ports to eMule would increase its performance. Right now, I'm trying to d/l a file with over 400 sources, and it took about 2.5 hours to begin.. and now it's d/ling from one person at 3Kb/s, and I'm on 1500/256 DSL with a highID.