is this the proof that dns replay made out on WAN interface, i logged something from the step1 and its like this:
step1 output: in (unknown 0) out: ether1-Wan, proto UDP, my dns server public IP address:53 → remote dns client that im using:59363, len 168
Yes, it is.
Tnx, ISP is telling me that they are not blocking anything, but 4 different client IPs cant receive DNS replay…i guess i will speak with them again.
replay = proigrati ponovo,
reply = odgovoriti (ili odgovor)
I’m a bit nervous about the firewall log showing the packet but the torch not, I don’t remember whether you did a sniff on the interface.
Where exactly (to which table & chain) have you placed the rule which has logged that packet?
Can it be that the “Torch” screen update time? i.e. between updates this happened hence did not show?
I finally got an answer from different section of ISP, and they give me the tech prospect which saying that they are blocking source port 53 from clients in order to maximize security…
So 3 times i was in contact with “some” technical support and they told me they are blocking nothing, but thats not the case…its really crazy when someone is not informed like that…