[00:06] *** gizmoguy has joined #arpnetworks [00:32] *** Seji has quit IRC (Read error: Connection reset by peer) [00:33] *** Seji has joined #arpnetworks [10:28] *** m0unds_ has joined #arpnetworks [13:40] ping [13:40] *** mnathani_ has quit IRC () [13:40] *** mnathani_ has joined #arpnetworks [19:31] *** mnathani_ has quit IRC (Ping timeout: 272 seconds) [19:49] *** mnathani_ has joined #arpnetworks [20:29] mnathani: pong [20:59] Does anyone have experience with configuring Unbound on FreeBSD? I've run into a problem with setting up forwarding for .lan, the TLD I use for LANs [21:03] whats the error [21:06] There is no error as yet, I haven't got that far. To begin with, the path for Unbound config files seems to be unstable. Both /etc/unbound (/var/unbound) and /usr/local/etc/unbound exist [21:08] From https://calomel.org/unbound_dns.html I read "Then place the following unbound.conf in place of your copy; i.e on the OpenBSD install the config file is located in /var/unbound/etc/unbound.conf , on FreeBSD 10.0 and earlier /usr/local/etc/unbound/unbound.conf and FreeBSD 10.1 /etc/unbound/unbound.conf" [21:09] I'm working with 10.2, with Unbound from ports, and it indeed seems to be the case that /var/unbound is where the conf files are expected to be, with /usr/local/etc/unbound containing only unbound.conf.sample (old cruft yet to be jettisoned I can only assume) [21:30] i would use /usr/local/etc/unbound/unbound.conf [21:33] i think /var/blah is the unbound that comes with the base OS [21:34] check out /etc/rc.d/local_unbound [21:34] all port configs usually go in /usr/local/etc [21:36] calomel is a bad site [21:36] openbsd uses /var/unbound [21:37] freebsd 9 uses /usr/local/etc [21:38] mjp_: That's what's strange about the /var/unbound location. In /etc/rc.d/local_unbound there is ": ${local_unbound_workdir:=/var/unbound}" [21:39] mjp_: I was careful to not select local_unbound to be installed by bsdinstalled, and I then installed it after the fact as a port [21:40] whats strange about that? [21:41] That it's not /usr/local/etc/unbound :-) [21:41] https://www.freebsd.org/doc/handbook/dirstructure.html [21:43] mjp_: Yes and? [22:04] I've figured out the problem. I was mixing up local_unbound_enable and unbound_enable in rc.conf. It was a dumb mistake [22:11] Which command will allow me to see where unbound is retrieving records from? (I want to verify selective forwarding is working correctly) [22:19] https://www.unbound.net/documentation/unbound-control.html [22:22] i have various freebsd's handy here [22:22] * mercutio takes al ook [22:22] unbound-control is assuming local_unbound, as `unbound-control stats` references an error "error: Could not open /var/unbound/unbound.conf: No such file or directory", despite the man page for unbound-control stating regarding the -c option "If not given the default config file /usr/local/etc/unbound/unbound.conf is used." which doesn't make sense to me [22:23] i have /var/unbound/conf.d/ on freebsd 10.1 [22:23] mercutio: You must have installed local_unbound with the OS in bsdinstall, correct? [22:23] and /var/unbound on freebsd 10 [22:23] and nothing at all on freebsd 9.1 [22:24] this is whatever arp is providing [22:24] maybe it's the default [22:24] arp isn't normally providing freebsd 10.1 due to some bugginess though [22:24] there should be 10.2 out soon though [22:25] i would use tcpdump to find out where unbound is directing stuff [22:25] I'm running 10.2 [22:25] unbound is part of base since 10.0, the installer just gives you the option to enable it [22:26] mercutio: I thought of that, however I'd like to figure out why the unbound-control utility is getting weird [22:26] what's being weird about it? [22:26] i love unbound-control :) [22:26] It's trying to open and use /var/unbound/unbound.conf when that isn't where my unbound.conf is located [as I'm not using local_unbound, but rather ports unbound] [22:27] why don't you use base unbound? [22:29] I'd like the latitude to upgrade it more frequently [22:31] if you're already on 10.2 you'll probably be on 11 soon [22:31] but yeah i suppose that's a reason [22:31] If by soon you mean one year from now [22:31] that's soon to me [22:32] I can dig that [22:32] it's not something i rush to update [22:34] `unbound-checkconf /usr/local/etc/unbound/unbound.conf` is returning "[1440997658] unbound-checkconf[806:0] fatal error: config file /usr/local/etc/unbound/unbound.conf is not inside chroot /var/unbound" [22:34] which unbound [22:34] I wish ports Unbound wasn't mixed up with local Unbound [22:35] usr/sbin/unbound [22:35] you should have /usr/local/sbin/unbound [22:35] if it's from ports [22:36] I do. Ok I think I understand. With local_unbound being bundled with base, it's imposing itself on pathing despite not being enabled [22:36] are you starting with /usr/local/etc/rc.d/unbound start [22:36] command="/usr/local/sbin/unbound" [22:36] rc.conf contains `unbound_enable=YES` so I would assume so [22:36] because that's specifiying /usr/local exactly [22:37] try starting manually with that [22:37] With which? [22:37] is local_unbound_enable="NO" ? [22:38] No [22:38] with /usr/local/etc/rc.d/unbound start [22:38] It isn't in rc.conf [22:38] it may be in /etc/defaults/rc.conf [22:38] Done [22:38] I'm sure ports Unbound is what's being started up as the forward zone entry I made to /usr/local/etc/unbound/unbound.conf took effect [22:38] i don't have 10.2 in front of me, i don't know if defaults changed. [22:39] it maybe that unbound-checkconf isn't pathed specifically [22:40] The bundled unbound is definitely taking path precedence [22:40] for unbound-checkconf specifically? [22:40] Correct [22:41] `unbound-checkconf /usr/local/etc/unbound/unbound.conf` suggests it's following path [22:41] i need gmake etc [22:49] hmm the rc.d has specific /usr/local/sbin/unbound-checkconf for me [22:49] with unbound 1.4.22_4 [22:59] I can't tell for certain using unbound-control lookup, but I think all lookups are going to the forward [23:00] http://pastebin.com/GFrvLyaq [23:05] The man page for unbound.conf is not clear to me on how exactly `forward-first` works. Can someone clarify it for me? [23:05] think it tries forward, and if that fails it falls back on going normal [23:06] from what i understand you want forward-zone: [23:06] name: "localdomain" [23:06] forward-addr: 192.168.1.4 [23:06] or something like that [23:06] so that *.localdomain gets directed to 192.168.1.4 [23:06] That's essentially what I have, and it's working well [23:06] should be fine then [23:07] What I'm trying to do is verify that example.com will not be forwarded [23:09] I woule assume not, however with unbound-control lookup google.com giving me no useful information, it's not easy to tell [23:10] only the domain in the naem gets forwarded [23:10] and subdomains of such [23:12] I verified that that is indeed the operation by adding a faux record for microsoft.com 1.2.3.4, `host microsoft.com`, and it returns the correct IP vs the placeholder [23:12] Thanks mercutio [23:13] Faux record to the forward zone name server, that is. Pardon the ambiguity