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. :-) .... Ken >> >> > Hi, >> > >> > squid doesn't like OpenBSD specific syntax on resolv.conf. >> > >> > # squid -N -d 3 >> > ... >> > 2014/01/26 17:58:51| DNS Socket created at [::], FD 5 >> > 2014/01/26 17:58:51| DNS Socket created at 0.0.0.0, FD 6 >> > 2014/01/26 17:58:51| Adding domain example.com from /etc/resolv.conf >> > 2014/01/26 17:58:51| Adding nameserver [127.0.0.1]:5330 from >> > /etc/resolv.conf >> > 2014/01/26 17:58:51| WARNING: rejecting '[127.0.0.1]:5330' as a name >> > server, because it is not a numeric IP address >> > ... >> > >> > $ cat /etc/resolv.conf >> > # Generated by iwn0 dhclient >> > search example.com >> > nameserver [127.0.0.1]:5330 >> > >> > resolv.conf(5) states: >> > ... >> > nameserver IPv4 address (in dot notation) or IPv6 address (in >> > hex-and- >> > colon notation) of a name server that the resolver should >> > query. Scoped IPv6 address notation is accepted as well >> > (see >> > inet6(4) for details). A non-standard port may also be >> > specified, with the host address enclosed in square >> > brackets. >> > For example: >> > >> > nameserver [10.0.0.1]:5353 >> > nameserver [::1]:5353 >> > >> > jirib >> > >> >
