Am 22.04.2014 19:17, schrieb John Griessen: > On 04/22/2014 12:02 PM, Erwan David wrote: >>>> In that case DNS should switch to TCP or use EDNS, both MUST be >>>> >>available in a modern installation, because DNS answers become larger >>>> >>with new features (IPv6 addresses, DNSSEC, etc.) >>> >Yes, but all it takes is one firewall that blocks TCP port 53 and the TCP >>> >fallback fails. Even on the modern internet you have to try to fit in a >>> >UDP >>> >packet if you want reliable service. >>> > >>> >Scott K >>> > >> No, that time is finished. Take a domain with just 2 MXes and an signed DNS >> >> dig +dnssec MX rail.eu.org -> 1248 bytes > > Is it possible to use IPv6 as a website address in a practical way yet? > If so, know some examples to study?
* it's off-topic * you need dual stack for al ot of years * there is not much to study * you have ipv6 on your server and a AAA record * but you need ipv4 because most clients have no ipv6
