New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dns-sortlist not recognized in network-config #2953
Comments
Launchpad user James Gibbins(jfgibbins) wrote on 2017-08-20T23:29:42.016463+00:00 Beuller? |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-09-07T14:39:04.084930+00:00 Is this site even monitored? |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-09T19:02:58.621486+00:00 3 months and not a single response? |
Launchpad user Scott Moser(smoser) wrote on 2017-10-18T14:45:52.257927+00:00 'sortlist' is new to me.. I've just never ran into it before. I can understand the usefulness of it, and you're desire to feed The problem that I see with it is that I'm not sure what to do with I don't want to add support to the networking configuration syntax As someone with experience here, do you have suggestions? Do I've marked this 'incomplete', feel free to set it back to 'new' if Thanks, and sorry for the slow reply. Scott |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-18T15:41:39.654824+00:00 Trying to do some testing real quick and research on systemd-resolve. Unfortunately it doesn't seem there is a cloud-init enabled version of artful yet on ubuntu: to really test. I have looked at what systemd-resolve is doing with it on 16.10 and earlier, and systemd-resolve seems to be oblivious to it, but then the system seems oblivious to systemd-resolve. I think given that 16.04 LTS still has 3.5 years of support, it still has a long life, and that adding sortlist, which I think may just be a one line change(?) will add the functionality for those who want/need it, but come systemd-resolve coming in to effect, I will have to wait til cloud-init artful is available to test. I will however continue to test against 17.10 as I'm able to get a cloud-init version functioning on lxd. I can't imagine Stephane will be far off on that one. He's usually pretty on the ball. And no worries about the slow reply. I never use launchpad, so maybe there is a way to ping you, but I don't know it. I'll have to remember you are on github though, and can ping you through that if really needed. Let me know what you think, but I think long term, it adds, and my instinct tells me no harm, but will test more. |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-18T15:45:24.968989+00:00 While I joked about it on github, it looks like sortlist from resolv may very well be superceded by RFC 3484 when falling under systemd-resolve. |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-18T15:59:24.511249+00:00 hmm...launchpad doesn't let me edit, so adding this from systemd-resolve docs: Alternatively, /etc/resolv.conf may be managed by other packages, in which case systemd-resolved will read it for DNS configuration data. In this mode of operation systemd-resolved is consumer rather than provider of this configuration file. |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-18T16:08:33+00:00 Hi Scott,Not sure if launchpad sends you notice of updates or not. Let me know if it does. Was surprised that this message came from your actual address, so you sent, or that's just how launchpad works, but added some comments on the ticket for you to see. I might be able to use packer to generate my own cloud-init version of artful til Stephane and the guys have a chance to add it to the ubuntu: image server. If so, I'll test with a system running systemd-resolve, not just for sort list, but the networking functions in general. My containers tend to be a little more complex than the average regarding network configs, ovs, multi-home, custom routing, vlans, etc. Blame it on my 30 years of networking, lol.
To: jfgibbins@yahoo.com 'sortlist' is new to me.. I've just never ran into it before. I can understand the usefulness of it, and you're desire to feed The problem that I see with it is that I'm not sure what to do with I don't want to add support to the networking configuration syntax As someone with experience here, do you have suggestions? Do I've marked this 'incomplete', feel free to set it back to 'new' if Thanks, and sorry for the slow reply. Scott ** Changed in: cloud-init (Ubuntu) -- Title: Status in cloud-init package in Ubuntu: Bug description: version: 1 However including the following line is not recognized: sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx'] Please add support for this standard nameserver option. To manage notifications about this bug go to: |
Launchpad user Scott Moser(smoser) wrote on 2017-10-18T17:03:42.074362+00:00 James, there are images in the ubuntu-daily: image repo, just not the ubuntu image repo. $ lxc launch ubuntu-daily:artful a1 127.0.0.53 is the systemd-resolved stub resolver.run "systemd-resolve --status" to see details about the actual nameservers.nameserver 127.0.0.53 search lxd |
Launchpad user Scott Moser(smoser) wrote on 2017-10-18T17:04:14.969217+00:00 (I do get email on bug comments, but as you've seen sometimes I miss them). |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-18T17:25:08+00:00 Appreciate that. I always forget about daily. So spun it up, and due to netplan, everything networking broke, as in network-config was ignored, and cloud-init couldn't use any of it. I'm guessing that netplan is supported using Networking Config Version 2 — Cloud-Init 17.1 documentation? I currently use Version 1. FYI, sortlist under the old method, ie version 1, does no harm under netplan. It in fact does the same as the rest of the network config, nothing, lol. | |
To: jfgibbins@yahoo.com James, there are images in the ubuntu-daily: image repo, just not the ubuntu $ lxc launch ubuntu-daily:artful a1 127.0.0.53 is the systemd-resolved stub resolver.run "systemd-resolve --status" to see details about the actual nameservers.nameserver 127.0.0.53 search lxd -- Title: Status in cloud-init package in Ubuntu: Bug description: version: 1 However including the following line is not recognized: sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx'] Please add support for this standard nameserver option. To manage notifications about this bug go to: |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-18T17:54:49.696428+00:00 Well, build with the ubuntu-daily, and there weren't even any files at /var/lib/cloud. I put up a post in lxc/lxd to inquire whether the image actually supports cloud-init under lxd with the new version. network-config, user-data, vendor-data, etc were all missing and non-functioning under lxd. Obviously more things have changed, as no adjustments were needed for 16.10 or 17.04. Very sad. :( |
Launchpad user Scott Moser(smoser) wrote on 2017-10-18T18:08:42.951290+00:00 James, sorry, can you show what you were doing ? ubuntu-daily definitely does work, with user-data and meta-data and such. |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-18T18:30:55.339843+00:00 Hey Scott, was going back and forth a bit with Stephane. Something goofy stil, as I was using ubuntu-daily:artful, which should have actually failed, cause daily doesn't have artful, but has 17.10, and images:, is the opposite. so even though I specified ubuntu-daily, it seemed to still be using the artful from images despite my command. I do have working instances of artful/17.10, whichever, lol, but cloud-enabled, yeah!!! It thankfully renders my version1 systax to netplan, nice job, I was worried I was going to have to rewrite tons of network stuff. Manually edit netplan to include sortlist, since cloud-init doesn't. Restart, etc, netplan/systemd-resolve completely ignores it as I was expecting. It does seem that netplan and systemd-resolve is going to defer to /etc/gai.conf which follows RFC 3484 as I mentioned previously. But that's going to be a whole other issue, and frankly, until I'm stuck using 17.10 and later, I really don't want to brush up on yet another RFC. I'm not that bored. In summary, sortlist, great for 17.04 and prior, which means useful on 16.04 LTS until 20.10. Completely ignored and harmless in 17.10 and if ubuntu keeps netplan, going forward. I know for my own uses, 16.04 will be around and in use for a long time. Even now, coming up on 3.5 years for 14.04, some apps and guides still aren't too happy about being on 16.04. I have a few 14.04s still left supporting a few apps to which I've never gotten cloud-init to handle networking well on it, so just manually edit or push a file to overwrite for those few instances. |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-18T18:46:42.856923+00:00 Damn, I just realized, netplan doesn't use ifup and ifdown now, does it? That's going to completely break my source-based routing. The important part is as follows: IF_GATEWAY="$(echo "$IF_ADDRESS" | cut -d. -f1-3).254" That doesn't by chance translate to netplan and cloud-init, does it? I can find routes: to, via, but nothing for adding to table. |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-27T19:00:06.261194+00:00 Hey Scott, |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-10-31T15:36:55+00:00 Hi Scott,I know you're aware of and dealing with netplan issues, but not if you're directly involved with it. But netplan has serious deficiencies and nowhere near as inclusive or as capable as the current system. Functions such as source-based routing, open vswitch support, etc. One release before an LTS seems far too late to introduce such a half-baked and untested package that is so central to network connectivity. Please tell me their not seriously considering going forward with it for the next LTS. If so, I may have to stay on 16.04 til 20.04 comes along, assuming they get it working by then.James
To: jfgibbins@yahoo.com ** Also affects: cloud-init ** Changed in: cloud-init -- Title: Status in cloud-init: Bug description: version: 1 However including the following line is not recognized: sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx'] Please add support for this standard nameserver option. To manage notifications about this bug go to: |
Launchpad user David Britton(dpb) wrote on 2017-11-01T20:42:36.954147+00:00 Hi James -- do you have an example #cloud-config that you can attach that sets up source-based routing (please sanitize first if required)? Thanks. |
Launchpad user James Gibbins(jfgibbins) wrote on 2017-11-01T21:17:15+00:00 Hi David,This ticket is for the source-list, which is for dns resolver and the config is as follows. Basically, if the interface is a loopback, dhcp, or already has a default gateway, it does nothing. For any other interface, it adds a default route to the route table causing all responses to inbound traffic to use the same interface to respond on. The email I sent late last night to your email, discusses what I've been able to find, in terms of using systemd-networkd, but requires ver 235, as well as some additional work in netplan and cloud-init to recognize all the values. P.S. systemd 235, which I saw is proposed for bionic beaver, adds quite a few nice functions, including "vrf".
To: jfgibbins@yahoo.com Hi James -- do you have an example #cloud-config that you can attach Thanks. -- Title: Status in cloud-init: Bug description: version: 1 However including the following line is not recognized: sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx'] Please add support for this standard nameserver option. To manage notifications about this bug go to: |
Launchpad user Dan Watkins(oddbloke) wrote on 2019-02-19T14:41:57.013906+00:00 Dropping this from the cloud-init Ubuntu package so we're just tracking it in one place. |
This bug was originally filed in Launchpad as LP: #1704402
Launchpad details
Launchpad user James Gibbins(jfgibbins) wrote on 2017-07-14T14:32:40.942560+00:00
I'm using LXD with Ubuntu images, and cloud-init to do initial setup of container. I'm not sure, but I believe the issue is in cloud-init, but would appreciate a pointer to the right location if not. Currently using network-config meta data, cloud-init takes the following config and converts correctly:
version: 1
config:
name: eth0
address: ['xx.xx.xx.xx']
search: ['example.local', 'example.org']
However including the following line is not recognized:
sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx']
Please add support for this standard nameserver option.
The text was updated successfully, but these errors were encountered: