MAAS unmanaged network set wrong DNS information

[lithium]

I'm trying to setup a MAAS with attached network topology. (see attached diagram.png file)

Main idea is to have a MAAS netwotk (10.10.10.0/24) with DHCP and DNS managed by MAAS to commissioning nodes, after node is successful commissioned, I setup node network like this in WebUI:

eth0 Physical fabric0 untagged 192.168.100.0/24 (DHCP)
eth1 Physical fabric0 untagged 10.10.10.0/24 (Unconfigured)

Where 192.168.100.0/24 is my LAN network where i'm going to access to node with juju or whatever.
and 10.10.10.0/24 network is only for commissioning/pxe etc

After i deploy a node with MAAS WebUI or juju bootstrap i can confirm that my local (LAN) dhcp/dns correctly configure the node

Ex:

---------------------------------
redelmann@litza:~$ ping maas-node-1
PING maas-node-1 (192.168.100.141) 56(84) bytes of data.
64 bytes from maas-node-1.localmaas (192.168.100.141): icmp_seq=1 ttl=64 time=0.354 ms
64 bytes from maas-node-1.localmaas (192.168.100.141): icmp_seq=2 ttl=64 time=0.340 ms
64 bytes from maas-node-1.localmaas (192.168.100.141): icmp_seq=3 ttl=64 time=0.383 ms
---------------------------------

but when i ssh to maas-node-1 and see /etc/resolv.conf this is what i see:

---------------------------------
# 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 192.168.100.1
nameserver 192.168.100.10
search localmaas
---------------------------------

MAAS automagic add herself as a DNS server. (See: nameserver 192.168.100.10)

Here it's not a problem because my real DNS 192.168.100.1 it's over MAAS DNS, but sometime "when i use juju bootstrap" my node resolv.conf contain:

---------------------------------
# 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 192.168.100.10
nameserver 192.168.100.1
search localmaas
---------------------------------

and if i ping maas-node-0 from inside node i get:

---------------------------------
ubuntu@maas-node-0:~$ ping maas-node-0
PING maas-node-0.localmaas (10.10.10.21) 56(84) bytes of data.
---------------------------------

but i should get ip from my LAN (192.168.100.0/24)

BTW: juju bootstrap fail with:
2016-02-14 19:20:08 WARNING juju.replicaset replicaset.go:98 Initiate: fetching replication status failed: cannot get replica set status: can't get local.system.replset config from self or any seed (EMPTYCONFIG)

Here curtin output:
http://paste.ubuntu.com/15060721/

and subnets output:
http://paste.ubuntu.com/15060537/

And just in case my maas interfaces settings:

---------------------------------
ubuntu@maas-server:~$ cat /etc/network/interfaces.d/*
auto eth0
iface eth0 inet static
  address 192.168.100.10
  netmask 255.255.255.0
  gateway 192.168.100.1
  dns-nameservers 192.168.100.1
auto eth1
iface eth1 inet static
  address 10.10.10.10
  netmask 255.255.255.0
  dns-nameservers 10.10.10.10 192.168.100.1
---------------------------------

---------------------------------
ubuntu@maas-server:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-================================-================================-============-===============================================================================
ii maas 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server provisioning libraries
---------------------------------

[Andres Rodriguez (andreserl)]

We believe this is no longer an issue in the latest releases of MAAS. Please upgrade to the latest version of MAAS, and If you believe this issue is still present, please re-open this bug report or file a new one.