NM fails to list IPv6 nameservers before IPv4 ones
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Fedora) |
Won't Fix
|
Medium
|
|||
network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
Description: Ubuntu 10.10
Release: 10.10
network-manager:
Asennettu: 0.8.1+git.
Ehdokas: 0.8.1+git.
Versiotaulukko:
*** 0.8.1+git.
500 http://
100 /var/lib/
0.
500 http://
When using dual-stack IPv4/IPv6 connectivity the nameservers are in wrong order in /etc/resolv.conf The IPv6 nameservers should be first.
Same bug: https:/
summary: |
- IPv6 Nameservers are not prioritised correctly in resolv.conf + NM fails to list IPv6 nameservers before IPv4 ones |
Changed in network-manager (Fedora): | |
importance: | Unknown → Medium |
status: | Unknown → Won't Fix |
Created attachment 467312
Proposed patch to correct /etc/resolv.conf ordering.
Description of problem:
In currently version of NetworkManager in Fedora, IPv6 DNS nameservers are getting prioritised last in /etc/resolv.conf this doesn't seem right compared to prioritization of IPv6/IPv4 in general IP stacks (for instance, web browsing).
Version-Release number of selected component (if applicable): 0.8.1-10. git20100831. fc14.x86_ 64
NetworkManager-
How reproducible:
Always
Steps to Reproduce:
1. Set up a dual stack IPv6/IPv4 network, in my case radvd is announcing IPv6 nameservers & IPs, dhcp is announcing IPv4 IPs & nameservers.
2.
3.
Actual results:
NetworkManager will write a /etc/resolv.conf in the following order:
domain <foo>
search <bar>
nameserver [IPv4 VPN Nameservers]
nameserver [IPv4 LAN Nameservers]
nameserver [IPv6 VPN Nameservers]
nameserver [IPv6 LAN Nameservers]
This means that DNS queries will happen over the IPv6 stack last.
Expected results:
My expected ordering is:
* IPv6 VPN Nameservers
* IPv4 VPN Nameservers
* IPv6 LAN Nameservers
* IPv4 LAN Nameservers
I prioritise IPv4 VPN over IPv6 LAN in consideration that there will be some IPv4 only VPN networks around for a while.
Additional info:
I have a patch that has worked over the last week on my home/personal laptop that corrects this issue. (Attached)