Bug 221760 - freebsd-update problems with some picky DNS
Summary: freebsd-update problems with some picky DNS
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 11.1-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-24 10:13 UTC by Maurizio Giunti
Modified: 2021-01-11 09:24 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maurizio Giunti 2017-08-24 10:13:38 UTC
Sometimes freebsd-update can't work because some DNS do not resolve domain with upcase chars.


Error I get:

# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 1 mirrors found.
Fetching public key from update1.FreeBSD.org... failed.
No mirrors remaining, giving up.

Workaround:

Edit /etc/freebsd-update.conf and change following line:

ServerName update.FreeBSD.org

into

ServerName update.freebsd.org


I know this is not exactly a FreeBSD problem, but it can prevent system updates on certain providers.
Comment 1 Leo Vandewoestijne 2021-01-11 09:24:00 UTC
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.