Comment 6 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 | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi, thanks for reading.
You are right, this is not a bind issue. It appears with ntp also.
I spoke about resolv.conf because it masked me the problem: it contains my 3 nameservers
But As I mentioned, when one server tries resolving using itself, if works. That's why I noticed lately the problem when adding a non-nameserver ubuntu.
Of course, I made my best to find any network issues, there a no firewall and all takes place in a HyperV network.
So, I asked a more general and simple question here : https:/
When I switch to ipv4 (resolving, ntp) with the same host, all is fine.
TO help reproduce, I'll add 2 more servers, strictly ipv6, one in Ubuntu 16.04 and one in 15.10 and check.
I'll tell later
Fred