Comment 3 for bug 1584042
Revision history for this message
| Frédéric Druilhet (frederic-druilhet) wrote Re: IPV6 resolving fails via udp (not tcp) from other server | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Just to add a point about how I noticed the bug. It as one important information.
I have 3 nameservers, all ipv6/4. No particular problem.
Problem occurred when I added a 4th Ubuntu server. This one installs fine as I set ip IPv4 first with the 3 nameservers ipv4 address. But, when I added the ipv6 interface, and all 3 nameservers with their ipv6 address, it failed. I spent a lot of time checking network, Ipv6, reinstalling Ubuntu till I end up notifying that as a real bug.
In fact, adding 3 ipv6 nameservers address changes the resolv.conf and the 3 nameservers stack is filled with ipv6 adresses. So, it leads to a non responding resolution.
I made some tests on my nameservers and noticed that they are in the same setup but, and thats the important discovery, they get a response with ipv6 when then request themselves. Server1 doesn't get a response from server2 et 3, but it does with server1. That's one I didn't noticed the bug because each nameserver has it's own address in the resolv.conf so requests end with responding
To Bypass the bug, each interface has only ipv4 nameserver addresses except on each nameserver where I left it's own ipv6 address in the interface setup