On 2014/01/27 03:51, Jiri B wrote: > On Mon, Jan 27, 2014 at 08:41:29AM +1300, Kenneth Westerback wrote: > > On 27 January 2014 08:32, Jiri B <ji...@devio.us> wrote: > > > On Mon, Jan 27, 2014 at 08:09:20AM +1300, Kenneth Westerback wrote: > > >> Dhclient will not generate such syntax in resolved.conf so I assume you > > >> are > > >> doing so via resolv.conf.tail or ... ? And if so, I guess you need to > > >> choose between squid and your local DNS port. > > > > > > Yes, I used resolv.conf.tail. Hmmm, squid does not seem to support > > > custom dns port anyway via a config option. > > > > > >> Or are you saying that there is a snort friendly syntax for this purpose > > >> that we should be using instead? > > > > > > I don't understand the question. > > > > > > > Since I don't know squid, I was asking if it did handle some other > > syntax that we might be able to add to resolv.conf consumers. "does > > not seem to support custom dns port" would seem to answer the > > question. :-) > > I submitted RFE - http://bugs.squid-cache.org/show_bug.cgi?id=4017. > > jirib
As a workaround I suggest running your local resolver on a different IP address. You can always create another loopback interface (lo1 etc) if you don't want it bound to an internet-accessible address.