[05:40] <roothorick> this is really bizarre. This machine isn't resolving LAN names, except its own, which it resolves completely wrong (not even the same subnet!)
[05:41] <roothorick> just updated it from 16.10
[05:45] <valorie> roothorick: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647031 ?
[05:48] <roothorick> oh, the local machine's name is resolving to 127.0.1.1
[05:48] <valorie> I don't know anything more about it but I remember this bug being discussed
[05:49] <valorie> because something related has affected me in 16.10
[05:49] <valorie> and a few others in 16.10 as well
[05:50] <roothorick> that doesn't seem like it
[05:50] <roothorick> Internet names resolve fine
[08:33] <roothorick> a number of things are making me think there's something seriously wrong network-wise
[08:33] <roothorick> no coherent pattern though
[08:54] <roothorick> so, I don't think it was the same issue, but
[08:55] <roothorick> I removed the execute bit from /lib/systemd/systemd-resolved and manually added a DNS server to resolv.conf
[08:55] <roothorick> and it fixed three seemingly unrelated problems in one fell swoop
[08:57] <roothorick> one of them was a thing that makes absolutely no sense for it to be affected by a hostname resolver
[08:57] <roothorick> namely, native Steam couldn't log in to its own store
[08:58] <roothorick> but it would still load
[08:59] <roothorick> now, how would I even begin to pinpoint the exact problem... hoo boy
[09:12] <roothorick> push comes to shove, I'll just keep resolved hacked out like this
[09:13] <roothorick> it'd be a disservice to not check on it periodically to see if it's fixed, though. Especially being a pre-release
[21:08] <PickledEggs> I'm having a strange boot issue since installing 17.04 - my dmesg output is here: http://paste.ubuntu.com/23824230/
[21:08] <PickledEggs> it looks like an issue with ip6_tables
[21:08] <PickledEggs> anybody experience anything similar?
[22:00] <roothorick> how DO I make lasting changes to resolve.conf?
[22:00] <roothorick> files in /etc/resolvconf/resolv.conf.d are getting ignored