Jaap, I ran the dig command, as suggested, for a period of time (about 1.5 hours). Unbound continued to respond without issue, so it looks like we are ok. I will do a little more testing, but it is looking like we can remove the source NAT.
Thank you for the suggestion, Paul On Wed, Jun 11, 2014 at 2:02 PM, Jaap Akkerhuis <[email protected]> wrote: > > Will unbound see this constant source IP/port as unusual, and block > further > DNS queries in a similar manner after a period of time? In other > words, > will we require the the source NAT with unbound, until we can fix the > buggy > gateways? > > As far as I know it won't do block on this. That is easely tested > to run something like: > > while true; do dig -b 127.0.0.1#8765 +short example.com; done > > on a (test server) which runs unbound as a resolver. > > jaap > -- *Paul Niemi, B.Sc., B.Eng.* | Networks and Servers Technician *Tbaytel *| 241 S. Vickers Street | Thunder Bay, Ontario | P7E 1J5 Tel: (807) 625-3043 www.tbaytel.net <https://anywhere.exchserver.com/owa/redir.aspx?C=470ce06163a045ee9da8a0bc65439d0c&ur> -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by e-mail if you have received this email by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
_______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
