Re: CVS commit: src/distrib/utils/sysinst

["Jonathan A. Kollasch" <jakllsch%kollasch.net@localhost>]

On Sun, Oct 30, 2011 at 11:07:04AM +0100, Martin Husemann wrote:
> On Sun, Oct 30, 2011 at 09:41:09AM +0100, Bernd Ernesti wrote:
> > > Log Message:
> > > As both of the "ns-wide.wide.ad.jp" and "light.imasy.or.jp" IPv6 resolvers
> > > now refuse my queries, replace them with "google-public-dns-a.google.com"
> > > and "google-public-dns-b.google.com".
> > 
> > IMHO they should be replaced with ?.root-servers.net entries and not a with
> > an address of a private company.
> 
> I don't understand why we offer this menu at all, shouldn't it just go
> away?

Bernd:

Those are not open resolvers, they are authoritative for . only.
I also doubt we want to put bind(8) into the ramdisk.

Martin:

Until RFC 6106 is usable by sysinst, and/or until it is widely deployed,
the menu must stay for people without IPv4 connectivity.  Unless you
want to enter a up-to-39-character address for the resolver or server
the sets are on manually.

I was somewhat hesitant to choose Google, however I sort of doubt
anyone wants to provide open resolvers these days.  Google has the
resources to prevent abuse of their open resolvers, and they have
motivation to keep them running.  The 'other' option where you
enter your own resolver's address is still there.

I can barely remember the 20 character unique-local address of my
resolvers, and I don't have extreme aversion to letting Google see
what addresses I'm resolving for the duration of sysinst.

If TNF can provide a open resolver on a stable IPv6 address for use
by sysinst, that'd be great.

        Jonathan Kollasch