MAAS doesn't allow specify port for Forward DNS server

Bug #2056050 reported by Andy Wu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Committed
High
Christian Grabowski
3.3
Won't Fix
High
Christian Grabowski
3.4
Fix Committed
High
Christian Grabowski
3.5
Fix Committed
High
Christian Grabowski

Bug Description

The current DNS settings in MAAS only allow the IP address of the name server for a zone forwarder. We need to add support for including a non standard port, eg <ip:port>

MAAS version: 3.4/stable

Related branches

summary: - MAAS doesn't allow specify port for DNS server
+ MAAS doesn't allow specify port for Forward DNS server
description: updated
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
Changed in maas:
importance: Medium → High
importance: High → Medium
Revision history for this message
Camille Rodriguez (camille.rodriguez) wrote :

subscribed field-high - affecting a customer deployment

Changed in maas:
importance: Medium → High
milestone: none → 3.5.0
Changed in maas:
assignee: nobody → Christian Grabowski (cgrabowski)
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Christian Grabowski (cgrabowski) wrote :

Upon further review, the 3.4 and 3.3 backports had to be reverted due to the addition of DB migrations. This fix will have to be available in 3.5 or newer.

Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

We're running into complications related to how Django migrations work, backporting the fix is not straightforward so we need to figure out a proper way forward.

Changed in maas:
milestone: 3.5.0 → 3.6.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.