Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Jan 2021 09:24:00 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 221760] freebsd-update problems with some picky DNS
Message-ID:  <bug-221760-227-q5ugta014z@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221760-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-221760-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221760

Leo Vandewoestijne <freebsd@dns.company> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |freebsd@dns.company

--- Comment #1 from Leo Vandewoestijne <freebsd@dns.company> ---
If ISP's filter on this, then I'm relative sure they break RFC's.

However, if the dialogs tells it brought you from update.FreeBSD.org to
update1.FreeBSD.org, then it looks like DNS is working.

Maybe this 2017 case failed on a human DNS error or cached entry to an old
target.

Going from update.FreeBSD.org to update1.FreeBSD.org indicates there was a
CNAME involved. I doubt this still is done like that, which probably also
improved this issue.

So in resume:
lower/upper seem to work fine, CNAME target may have failed.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221760-227-q5ugta014z>