Comment 17 for bug 1575940

Ok, I bootstrapped with the requested --config setting, and then did:

juju deploy ubuntu ubuntu-lxd --to lxd:0 <-- gave me 0/lxd/0
juju add-machine lxd:0 <-- gave me 0/lxd/1

MODEL CONTROLLER CLOUD VERSION
controller scapecontroller scapestack 2.0-beta9

APP STATUS EXPOSED ORIGIN CHARM REV OS
ubuntu-lxd unknown false jujucharms ubuntu 0 ubuntu

UNIT WORKLOAD AGENT MACHINE PORTS PUBLIC-ADDRESS MESSAGE
ubuntu-lxd/0 unknown idle 0/lxd/0 10.96.13.53

MACHINE STATE DNS INS-ID SERIES AZ
0 started 10.96.13.49 /MAAS/api/1.0/nodes/node-32fdcb12-546c-11e4-b3f2-2c59e54ace74/ xenial dawn
  0/lxd/0 started 10.96.13.53 juju-6a81a0-0-lxd-0 xenial
  0/lxd/1 started 10.96.13.54 juju-6a81a0-0-lxd-1 xenial

Now /etc/resolv.conf:
$ juju-2.0 run --all 'sudo cat /etc/resolv.conf'
- MachineId: "0"
  Stdout: |
    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 10.96.0.10
    search scapestack
- MachineId: 0/lxd/0
  Stderr: |
    sudo: unable to resolve host juju-6a81a0-0-lxd-0
  Stdout: |
    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 10.96.0.10
- MachineId: 0/lxd/1
  Stderr: |
    sudo: unable to resolve host juju-6a81a0-0-lxd-1
  Stdout: |
    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 10.96.0.10

Only machine 0 has the "search <domain>" line.

Didn't try with lxc because beta9 now only supports lxd.