Found out that the ip's are listed in /run/resolvconf/interface/original.resolvconf
On Fri, Jul 24, 2015 at 4:09 PM, Niels Goossens <[email protected]> wrote: > Christopher, > > Instance (Ubuntu 14.04 lx-brand 20150601 > 5.11 joyent_20150625T055522Z > > On Fri, Jul 24, 2015 at 2:47 PM, Christopher Horrell < > [email protected]> wrote: > >> Which image are you using? Newer Ubuntu LX images (20150601 and up) fixed >> an issue where there were leftover resolvconf entries (in >> /etc/resolvconf/resolv.conf.d/) from when the image was created. Also, what >> platform are you using? >> >> >> >> -- >> Christopher Horrell >> Manager, Solutions Engineering >> Joyent Inc. >> http://www.joyent.com/ >> >> >> On Fri, Jul 24, 2015 at 8:42 AM, Niels Goossens <[email protected]> >> wrote: >> >>> Thanks. The 216 ip address looks like it's from one of Joyent's >>> datacenters if I read the traceroute correctly. >>> >>> The things is I thought I did override the settings, I've >>> added "resolvers": ["10.10.1.7"] (which is my own DNS) to the json, but it >>> still creates the Google ones in the LX zone. If I look in the zone itself, >>> 10.10.1.7 is added to tail (/etc/resolvconf/resolv.conf.d/tail), but both >>> base and head are empty. If I look in /etc/resolv.conf, I see >>> >>> nameserver 8.8.8.8 >>> nameserver 8.8.4.4 >>> nameserver 216.52.1.1 >>> # AUTOMATIC ZONE CONFIG >>> nameserver 10.10.1.7 >>> If I do 'vmadm get' for that zone, I only see 10.10.1.7. To make it >>> interesting, not every LX zone I create has this behaviour and I have yet >>> to find out why... >>> >>> Kind regards, >>> >>> Niels >>> >>> On Fri, Jul 24, 2015 at 11:36 AM, Blake Irvin <[email protected]> wrote: >>> >>>> Yeah that’s right. These are just what are commonly considered sane >>>> defaults for resolvers (assuming you want your instance to be able to do >>>> DNS resolution upon boot, which most of us do). And like Cody says, you >>>> can override if you need to :) >>>> >>>> >>>> On Jul 24, 2015, at 2:39 AM, Cody Mello <[email protected]> wrote: >>>> >>>> Hi Niels, >>>> >>>> The values in /etc/resolv.conf come from the resolvers field for the >>>> VM. If you run: >>>> >>>> vmadm get <uuid> >>>> >>>> And look for the resolvers field, you'll see what it's using for these >>>> fields. The first two values in that list are Google's DNS resolvers. I'm >>>> not familiar with the third one, but it seems to be related to a company >>>> called Internap. If you want to change these values, take a look at the >>>> vmadm(1m) man page for information on the update subcommand. (You'll also >>>> want to take a look at the maintain_resolvers field, since I don't believe >>>> it's on by default.) >>>> >>>> - Cody >>>> >>>> On Thu, Jul 23, 2015 at 4:53 PM, Niels Goossens <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> After spinning up an Ubuntu 14.04 LX instance, its resolv.conf >>>>> contains: >>>>> >>>>> nameserver 8.8.8.8 >>>>> nameserver 8.8.4.4 >>>>> nameserver 216.52.1.1 >>>>> >>>>> I wonder where this comes from - it is not something I have put in >>>>> there. An LX instance I spun up earlier did not have this, but I cannot >>>>> figure out the difference between these instances. The json and base >>>>> image (a21a64a0-0809-11e5-a64f-ff80e8e8086f) >>>>> are the same. >>>>> >>>>> Has anyone witnessed this behaviour? >>>>> >>>>> Kind regards, >>>>> >>>>> Niels >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >> *smartos-discuss* | Archives >> <https://www.listbox.com/member/archive/184463/=now> >> <https://www.listbox.com/member/archive/rss/184463/26373474-5e129015> | >> Modify >> <https://www.listbox.com/member/?&;> >> Your Subscription <http://www.listbox.com> >> > > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
