Comment 6 for bug 1776604
Revision history for this message
| Andres Rodriguez (andreserl) wrote Re: [Bug 1776604] Re: default DNS IP for node from unexpected interface (not always first interface or same network) | #6 |
Hi Trent,
MAAS 2.3 -> 2.4 has not changed anything with regards to DNS. So updating
the record should be completely possible. Could you please provide a list
of commands with examples outputs?
On Mon, Jul 9, 2018 at 11:59 PM, Trent Lloyd <email address hidden>
wrote:
> I have a customer using 2.3 who needs to update the DNS record for their
> machine to be the correct (primary) interface in this scenario.
> Unfortunately in 2.3 it seems you cannot update the existing DNS record
> like you can in 2.4 (maas dnsresources read does not return any of the
> machine hostname records, thus you can't update them - and if you create
> a record alongside it - DNS returns both IPs instead of replacing the
> auto generated record)
>
> Is there some other way we can work around this issue on 2.3? As the
> customer is on Xenial, it seems 2.4 is not available for Xenial so it is
> not feasible to upgrade to 2.4 for them. Thus we need a fix or
> workaround for 2.3.
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https:/
>
> Title:
> default DNS IP for node from unexpected interface (not always first
> interface or same network)
>
> To manage notifications about this bug go to:
> https:/
>
> Launchpad-
> Launchpad-Bug: product=maas; milestone=2.5.0; status=Incomplete;
> importance=High; assignee=None;
> Launchpad-Bug: product=maas; productseries=2.4; milestone=2.4.1;
> status=New; importance=High; assignee=None;
> Launchpad-Bug-Tags: internal sts
> Launchpad-
> Launchpad-
> Launchpad-
> Launchpad-
> Launchpad-
> Launchpad-
> Launchpad-
> Launchpad-
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer