Attila Nagy wrote:
W.C.A. Wijngaards wrote:
Are those replies from authority servers? That arrive just after unbound
times out and closes the socket?
I'm not sure I understand this correctly. What we do is the following:
During trying to figuring out why does the "dropped due to no socket"
counter grows, I turned on net.inet.udp.log_in_vain, which logs what
connections couldn't find a socket.
And I quickly understood the above. :)
Yes, they are the answers from authoritative servers.
I don't know how long unbound waits for an answer, but I see about 10-30
lines per second per server from this. Do you think it's normal? (there
are about 4k qps currently)
May 30 14:25:21 ns Connection attempt to UDP m.y.i.p:42849 from
193.230.161.4:53
May 30 14:25:21 ns Connection attempt to UDP m.y.i.p:29188 from
202.103.224.70:53
May 30 14:25:21 ns Connection attempt to UDP m.y.i.p:6351 from
202.67.10.90:53
May 30 14:25:21 ns Connection attempt to UDP m.y.i.p:10611 from
202.67.10.90:53
Thanks,
_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
