After deploying a host with multiple IPs, I have issues resolving the fqdn because there are multiple DNS A records that point to ALL the IPs.
To fix, I restart the snap, that restarts bind, but it is annoying.
Thank you
After deploying a host with multiple IPs, I have issues resolving the fqdn because there are multiple DNS A records that point to ALL the IPs.
To fix, I restart the snap, that restarts bind, but it is annoying.
Thank you
Hi @zmance
Could you please open a bug on launchpad with the exact steps to reproduce it?
Thanks, appreciate it!
Hi @r00ta I have no problem opening a bug, but I’m not really doing anything special. It happens at random when deploying.
I can confirm this also happens in v3.4~rc2.
I will open a bug.
Thanks! Appreciate it!
May I kindly ask you to try also with 3.2? We did some changes on DNS in 3.3, so it would help us to understand if we have a regression in 3.3 and 3.4.
Sadly this is a production environment, and I don’t have a test env.
However, I do not recall seeing the issue when running 3.2
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
FYI the bug is now reported as Bug #2046255 “For every interface MAAS is adding an A record for...” : Bugs : MAAS
@zmance we fixed the bug and backported it to 3.4. In case you want to give it a try you can use 3.4/edge
.
In case you find any other issue please don’t hesitate to let us know