Comment 2 for bug 1576116
Revision history for this message
| Jacek Nykis (jacekn) wrote Re: DNS resolver added to loopback | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I uploaded curtin and /etc/network/
https:/
Please don't share outside of the company.
We have been using full external DHCP for some time and it always worked for us. I don't mean to say that this method is good or should be supported just want to point out that even if unsupported it still works just fine. I think it's unrelated to this problem though.
I can think of situations where adding MAAS as resolver on every host will cause problems. For example if MAAS DNS does not have full view of all zones but you force it on top of what is coming from DHCP or config management systems can end up with intermittent resolution problems for some hosts.
Another scenario is one we've just hit - firewalls blocking access to MAAS DNS.
If this behaviour can't be changed maybe there is a way to make it more visible and obvious to avoid surprises?