Yamaban wrote:
On Tue, 6 Oct 2015 23:20, Per Jessen <per@...> wrote:
Yamaban wrote:
On Tue, 6 Oct 2015 10:45, Per Jessen <per@...> wrote:
Carlos E. R. wrote:
On 2015-10-05 13:07, Bjoern Voigt wrote:
Having a running RADVD or DHCPv6 server on the router or somewhere else in the LAN does not necessary mean, that the Internet provider offers IPv6 connectivity. Also a temporary situation may change from time to time.
Yes, that is the issue precisely.
Apparently it is not possible a solution like letting the system know it should not use IPv6 on internet, only on the local network.
"ipv6 internet" and "ipv6 local network" are concepts you apply (e.g. by different address ranges), but the network stack does not know about it. Same as for IPv4. (ignoring RFC1918).
Or having the DNS not answering with Ipv6 addresses, even if it finds them.
A DNS server that does not respond to AAAA queries is not really a DNS server.
Oh, yes that would be ugly and introducing timeouts.
Correct would be a answer of "NXDOMAIN" on all AAAA queries for "noipv6" or "onlyipv4" configurations.
Uh no - if your application wants an AAAA address, it is not up to the nameserver to say "well, you can't have it". IMHO.
Yes, and No.
Such a solution has its place, esp. if your ISP makes working native ipv6 configuration impossible. (Hello, Vodafone)
A answr of NXDOMAIN can be cached, while a no-responce will be repeated for EVERY future dns request, and running into time-out EVERY time. Your customers will be deliriuosly happy with a 30-60sec. timeout for every DNS request in their applications. You can feel the hate wafting of.
A dns-server / dns-repeater should provide the possiblity to configure such a "no-valid-ipv6", or at least "no-valid-non-local-ipv6" response, even better if also the other way round, "ipv4-only-as-mapped-ipv6" is possible to configure.
In an ideal world such crutches would not be needed, but, hello reality.
IMHO a clear answer (NXDOMAIN) is better than blocking / dropping / ignoring a "AAAA" request. Less timeouts, and a defined behaviour.
I guess I don't quite appreciate when this would be required, but yes, any clear answer is better than no answer, absolutely. Still, it doesn't seem to me to be a job for the nameserver to determine what is good for the application or not. -- Per Jessen, Zürich (15.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org