[08:12] Good morning [11:33] Should I install haveged? I read it as possible solution to long post-boot wait times on a headless system. [11:35] jink: i always install preload & haveged on my ubuntu installs, on desktop [11:36] Cool, thanks. [11:40] Let's try if this works, brb. :P [11:46] It still boots, so that's good. :P [11:47] Seems to be faster, too. [11:47] By about 70 seconds. [14:51] jink: I recommend including haveged all the time [14:51] because it helps to generate *more* entropy for when it needs random generation and such [19:14] i'm trying to get bind9 to bind to my ipv6 address on ens160, i have 'listen-on-v6 { any;} ;' in my bind9 config. It loads and binds to localhost on ipv4, but i dont find it ever binding to my ipv6 addresses. the boxes works over ipv6, wondering if there is something obvious i'm missing on ubuntu 20.04? this should be super straight forward; done it a bunch of times going back to freebsd 4.10 [19:15] ipv6 is configured by slacc, i wonder if thats an issue [19:16] xibalba: have you checked the log? bind usually requires the interface to have an address in the prefix you're allocating. See "journalctl -u isc-dhcp-server -n 50" [19:18] no errors in the logs, i only see it binding to my ipv4 addr. "listening on IPv4 interface lo, 127.0.0.1#53" no mention of ipv6 [19:19] i'm going to try and bind nginx to ipv6 and see if that works, maybe my issue is elsewhere [19:22] ok, nginx binds to my ipv6 address just fine [19:30] xibalba: then I suspect your /etc/dhcp/dhcp6d.conf isn't being read [19:32] i'm not using any dhcp here [19:32] netstat should show something bound to ipv6 on udp, correct? [19:32] haha sorry, got my wrong head on! [19:33] no problem at all [19:33] you know maybe netstat just isn't showing the socket bound to udp6 [19:33] tcpdump shows the traffic came in [19:34] xibalba: how about "sudo ss -nlutp sport = 53" [19:35] i still only 127.0.0.1 [19:35] going to see if bind responds to me in just a moment, had to update my bind acl [19:35] xibalba: ok, which file have you declared the listen-on-v6 in? [19:36] - /etc/bind/named.conf.options [19:36] xibalba: and, is that file being included when bind reads the configs? [19:36] correct, i will triple validate one moment [19:37] confirmed, the files paths are correct [19:38] i see the packet come in, but no response as expected -- 2600:1f16:195:d3bb:c25:a00b:245f:f41f → 2600:ABCD:a::20 DNS 90 Standard query 0xd38c A google.com [19:39] xibalba: if you restart bind9 now, does it start listening on those v6 sockets? [19:39] xibalba: I'm looking on mine which does IPv6, let's see if I can spot any clues [19:39] sdeziel, negative it does not bind to the v6 sockets. i'll try again and verify w/the ss command TJ- pointed out [19:39] 'ss' shows: udp UNCONN 0 0 [::]:53 [::]:* users:(("named",pid=1328,fd=512)) [19:40] yeh mine only says, 127.0.0.53%lo:53 , how strange [19:40] opps syntax error in my config, one moment [19:41] xibalba: that's usually systemd-resolved stub listener [19:41] netstat -anp | grep named [19:41] -- shows named as the process ID name udp 0 0 127.0.0.1:53 0.0.0.0:* 2558/named [19:42] xibalba: in the journalctl output, immediately before the listening on IPv4... I see "listening on IPv6 interfaces, port 53" [19:42] i do not [19:43] enable debug output and launch from command-line to tell what it is doing maybe? [19:43] good idea [19:43] xibalba: I'd run 'ps aux| grep named' to check if it's not running as 'named -4' or something [19:43] ahhhhh [19:43] ahhhhhhh [19:43] sdeziel, ! [19:43] - /usr/sbin/named -f -4 -u bind [19:43] cool [19:43] winner winner chicken dinner [19:44] thank you [19:44] yw [19:44] now where to change that ... heading to google! [19:44] xibalba: /etc/default/named [19:44] thank you both! === _KaszpiR__ is now known as _KaszpiR_ [19:47] I did look at the default/bind9 but mine had nothing but -u bind so assumed it was default [19:53] v6 binding is default in Ubuntu's bind9 install TJ- - `listen-on-v6` in /etc/bind/named.default.options handles that [19:53] but it can easily be disabled by saying "none" instead of "any" in that config option [19:54] teward: that's what I assumed, so apparently xibalba had a custom config [19:54] unless you're on an *ancient* version of BIND [19:54] TJ-: in which case they can simply add `listen-on-v6 { none; };` to their `options { ... }` block in their config [19:54] and achieve the same goal [19:54] just for future ;) [19:55] though xibalba is around still so they can read :P [19:55] that's simple compared to getting to grips with bird :) [19:55] i should point out that i'm 80% fluent in BIND's default config setup on Ubuntu - I use it as the recursive DNS system for my network xD [19:55] and the only DNS server that is allowed to be used on my network xD [19:58] hey sorry stepped away to get lunch [19:59] yeh i'm using bind9 for local recursion from my networks, and auth servers running up in aws for PTR records [20:00] i dont recall putting in -4 into /etc/defaults/named, this was from a VM I built ~8 months ago though [20:04] the joys of non version controlled configs :) [20:13] xibalba: sounds like you're missing options in your config then [20:13] or certain items in the options block [22:13] my entire network is ipv6 only . i'm trying to do "apt update" on this box and it keeps failing, it can't resolve us.archive.ubuntu.com from the dns server. [22:14] tshark from the dns server looks like it's asking for AAAA but gets back A [22:14] → 2001:500:2::c DNS 136 Standard query 0xe1f5 AAAA ns2.canonical.com OPT [22:14] what about just archive.ubuntu.com [22:15] DNS 755 Standard query response 0x3427 AAAA ns2.canonical.com NS ns1.canonical.com NS ns2.canonical. [22:15] com NS ns3.canonical.com NSEC3 RRSIG NSEC3 RRSIG A 91.189.94.173 A 91.189.95.3 A 91.189.91.139 OPT is what i see responded backin tshark [22:15] i'll try mybalzitch [22:16] no dice, something must be wrong w/my bind config [22:17] ;; ANSWER SECTION: [22:17] us.archive.ubuntu.com. 43 IN AAAA 2001:67c:1562::18 [22:17] works for me [22:17] so yeah check your bind [22:19] queries for AAAA against my local recursors and both 9.9.9.9 and 8.8.8.8 all gave back ipv6 addresses for me [22:20] is your recursor turning AAAA queries into ANY queries perhaps? [22:25] i'm not certain, i'll look into that. [22:25] i just have a basic config for the moment [22:25] https://paste.ubuntu.com/p/g2FfgSHpRz/ [22:33] hmm can get the AAAA back for google.com [22:34] for ns2.canonical.com have a quad A ? [22:53] I don't see one when resolving via quad9 [22:56] i only get an A when checking ns1.canonical.com [22:56] so my ipv6 only box can't seem to connect [23:17] 9.9.9.9 gives me an AAAA reply [23:19] do you get a quad A for ns1.canonical.com [23:19] yup [23:39] host -t AAAA ns1.canonical.com 8.8.8.8 [23:39] says ns1.canonical.com has no AAAA record [23:40] right [23:40] oh, sorry ns1 [23:40] I thought you meant us.archive, which you were trying before [23:40] @ ns1 [23:41] yeah I get no AAAA reply for ns1 either