Why ignore new name server if 3 name servers exists
Bug #1892447 reported by
Pengpeng Sun
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Hi team,
This might be a question which has been asked by someone else, but I did NOT find related bugs by searching.
See https:/
Thanks,
Pengpeng
Changed in cloud-init (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
Hi Pengpeng,
I think it boils down to arbitrary choice: we either need to discard the head or the tail of the list, and the current implementation discards the tail. I think the most common way to order nameservers is by decreasing priority, so the current implementation is the least surprising to me.
Do you have a specific reason to ask for the other way around?
Thanks!
Paride