svn commit: r366186 - in head/usr.sbin: bsdconfig/share/media bsdinstall/scripts

Warner Losh imp at bsdimp.com
Sat Sep 26 19:22:30 UTC 2020


On Sat, Sep 26, 2020 at 12:54 PM Niclas Zeising <zeising at freebsd.org> wrote:

> On 2020-09-26 20:28, Rodney W. Grimes wrote:
> >> On 2020-09-26 20:12, Rodney W. Grimes wrote:
> >>>> Author: zeising (doc,ports committer)
> >>>> Date: Sat Sep 26 16:27:09 2020
> >>>> New Revision: 366186
> >>>> URL: https://svnweb.freebsd.org/changeset/base/366186
> >>>>
> >>>> Log:
> >>>>     bsdconfig, bsdinstall: Prune dead mirrors
> >>>>
> >>>>     Prune dead mirrors from the list of mirrors in bsdconfig and
> bsdinstall.
> >>>>     All these return NXDOMAIN when trying to resolve them.
> >>>
> >>> This seems like the wrong place to fix it, as this does
> >>> nothing for all the "shipped" releases that contain the
> >>> old values.  Shouldnt these all just be CNAMED in dns
> >>> to a nearest replacement resource?
> >>>
> >>>
> >>
> >> Considering that we don't actually have control of the subdomans
> >> (CC.freebsd.org) ourselves, that is trickier than it might sound.
> >
> > How can freebsd.org NOT have ultimate control over deligations?
> > If things have become "lame" in a deligated zone the deligation
> > can and should be pulled and replaced with local data.
> >
> > This is cc.freebsd.org, not freebsd.org.cc!
>
> I am the wrong person to answer that question.
>
> In this case, things have not become lame.  For instance, the names
> ervers for se.freebsd.org work fine, but ftp3.se and ftp6.se records are
> removed.  Same for ru.freebsd.org and ftp4.ru.
> I'm merely pointing out that changing ftp.CC.freebsd.org usually
> requires contacting the person(s) maintaining the CC.freebsd.org zone,
> which is usually not the project.
>

It's usually people associated with the project in some way, but who might
not be as responsive as cluster admin. These domains have been delegated,
so we have to get the delegated admin to make the changes, which can take a
bit of time to chase down and doesn't lend itself to easy / automated
coping with this situation.

Warner


More information about the svn-src-head mailing list