>> >I'm pointing out that due to the configuration change that will follow
>> >from deployment of v6 roots it will be comparatively easy to reach all
>> >the caching resolvers (i.e. name servers) on v6 transport to ensure
>> >that they all do AAAA synthesis.
>> isn't it just a root.hint change, not a server replacement?
>Well, if you are running in a forwarding configuration *with your
>present server* and replace the root.hint file with one that includes
>v6 glue for one or several roots not much will happen. So there is no
>point to it.
>
>Because you are using a forwarding configuration.
I don't understand what you are saying, AT ALL.
I'm not using forwarding configuration. you must have some assumption
in your head which is not presented here.
itojun
- Re: (ngtrans) Joint DNS... Jun-ichiro itojun Hagino
- Re: (ngtrans) Joint DNS... Robert Elz
- Re: (ngtrans) Joint DNS... Nathan Jones
- Re: (ngtrans) Joint DNS... Jun-ichiro itojun Hagino
- Re: (ngtrans) Joint DNS... Johan Ihren
- Re: (ngtrans) Joint DNS... Nathan Jones
- Re: (ngtrans) Joint DNS... Jun-ichiro itojun Hagino
- Re: (ngtrans) Joint DNS... Johan Ihren
- Re: (ngtrans) Joint DNS... Alan Barrett
- Re: (ngtrans) Joint DNS... Johan Ihren
- Re: (ngtrans) Joint DNS... Jun-ichiro itojun Hagino
- Re: (ngtrans) Joint DNS... Johan Ihren
- Re: (ngtrans) Joint DNS... Jun-ichiro itojun Hagino
- Re: (ngtrans) Joint DNS... Johan Ihren
- Re: (ngtrans) Joint DNSEXT & NGTRANS summary D. J. Bernstein
- Re: (ngtrans) Joint DNSEXT & NGTRANS summary Dancer Vesperman
- RE: (ngtrans) Joint DNSEXT & NGTRANS summary Christian Huitema
