[RFE] use network's dns_domain to generate dns_assignment
Bug #1580588 reported by
yong sheng gong
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Miguel Lavalle | ||
neutron (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Problem:
currently, the port's dns_assignment is generated by combining the dns_name and conf.dns_domain
even if the dns_domain of port's network is given.
expectation:
generate the dns_assignment according to the dns_domain of port's network, which will scope the dnsname by
network instead of each neutron deployment.
tags: | added: l3-ipam-dhcp |
summary: |
- use network's dns_domain to generate dns_assignment + [RFE] use network's dns_domain to generate dns_assignment |
Changed in neutron: | |
importance: | Undecided → Wishlist |
assignee: | nobody → Miguel Lavalle (minsel) |
tags: |
added: rfe-postponed removed: rfe |
Changed in neutron (Ubuntu): | |
status: | New → Won't Fix |
To post a comment you must log in.
Essentially, this request is to override the dns domain used my dnsmasq on a network with the dns_domain attribute on the network. This changes the behavior without changing the API which could be a surprise to some. I actually thought this was what we were going to do when first introducing the dns_domain attribute to the network. So, from my perspective, it is a bug. But, apparently this was the designed behavior.
I kind of think we should do this but we might be trapped by backwards compatibility.