[2.0rc1] MAAS does not respect default subnet's DNS server when choosing default DNS
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Unassigned | ||
| 1.9 |
Won't Fix
|
Medium
|
Unassigned | ||
| 2.0 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
I deployed a system that uses external DHCP. Everything worked fine with exception of extra DNS server added to the config. This extra resolver is MAAS region controller and my systems don't have access to it on port 53. This causes delays in DNS resolution which then affects ssh and other things so we need to remove it before we can use the system in production.
I noticed that the problematic entry is added to the loopback interface:
auto lo
iface lo inet loopback
dns-nameservers 91.189.XX.XX
dns-search maas master-XXX
Adding region controller as resolver can be useful in some scenarios but it will break in others, especially in bigger environments with firewalls between subnets.
Can you provide option to control this feature on per subnet basis?
un maas <none> <none> (no description available)
ii maas-cli 1.9.1+bzr4543-
un maas-cluster-
ii maas-common 1.9.1+bzr4543-
un maas-dhcp <none> <none> (no description available)
ii maas-dns 1.9.1+bzr4543-
ii maas-proxy 1.9.1+bzr4543-
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.1+bzr4543-
ii python-maas-client 1.9.1+bzr4543-
ii python-
Related branches
- Gavin Panella (community): Approve
-
Diff: 343 lines (+220/-17)4 files modifiedsrc/maasserver/models/node.py (+60/-5)
src/maasserver/models/tests/test_node.py (+155/-0)
src/maasserver/preseed_network.py (+3/-6)
src/maasserver/tests/test_preseed_network.py (+2/-6)
- Mike Pontillo (community): Approve
-
Diff: 366 lines (+225/-17)5 files modifieddocs/changelog.rst (+5/-0)
src/maasserver/models/node.py (+60/-5)
src/maasserver/models/tests/test_node.py (+155/-0)
src/maasserver/preseed_network.py (+3/-6)
src/maasserver/tests/test_preseed_network.py (+2/-6)
- Andres Rodriguez (community): Approve
-
Diff: 90 lines (+54/-6)2 files modifieddebian/changelog (+44/-0)
debian/maas-region-controller.postinst (+10/-6)
| Andres Rodriguez (andreserl) wrote | #1 |
| summary: |
- MAAS adds regions controller as DNS resolver + DNS resolver added to loopback |
| Changed in maas: | |
| status: | New → Incomplete |
| Jacek Nykis (jacekn) wrote Re: DNS resolver added to loopback | #2 |
| Changed in maas: | |
| status: | Incomplete → New |
| Blake Rouse (blake-rouse) wrote | #3 |
| summary: |
- DNS resolver added to loopback + MAAS adds regions controller as DNS resolver |
| Changed in maas: | |
| milestone: | none → 2.0.0 |
| status: | New → Triaged |
| Changed in maas: | |
| status: | Triaged → New |
| Changed in maas: | |
| milestone: | 2.0.0 → 2.1.0 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Mike Pontillo (mpontillo) wrote Re: MAAS adds regions controller as DNS resolver | #4 |
| Haw Loeung (hloeung) wrote | #5 |
| summary: |
- MAAS adds regions controller as DNS resolver + [1.9,2.0rc1] MAAS does not respect default subnet's DNS server when + choosing default DNS |
| summary: |
- [1.9,2.0rc1] MAAS does not respect default subnet's DNS server when - choosing default DNS + [2.0rc1] MAAS does not respect default subnet's DNS server when choosing + default DNS |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| milestone: | 2.0.1 → none |
Hi Jacek,
MAAS doesn't support full external DHCP / DNS. And it will always use MAAS' region as DNS server, provided that is in MAAS where you assign the names of the machines will have on deployment.
You can, however, add a different resolver per subnet in MAAS, however, again, MAAS region will always be added.
Now the fact that it is adding it to loop back is strange provided that MAAS doesn't write loop back interface. Can you provide your e/n/I and get the curtin config for such node?