What's up with Macports' DNS?

[Dave Horsfall]

On Wed, 28 May 2025, Joshua Root wrote:

> >      Synchronizing local ports tree
> > fromrsync://rsync.macports.org/macports/release/tarballs/ports.tar
> >      rsync: getaddrinfo: rsync.macports.org 873: nodename nor servname
> > provided, or not known
> >      rsync error: error in socket IO (code 10) at
> > /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52.0.1/rsync/clientserver.c(106)
> > [receiver=2.6.9]
> 
> Hard to say. When this happens for you, you could check if a different DNS
> server than what you usually use is able to resolve the hostname, with a
> command like:

Well, I dunno; it worked this time (after failing two weeks in a row)...

I haven't changed anything in the nameserver department, so I'm baffled.

To summarise: each Sunday I run "port -u uninstall" followed on the Monday 
by "port selfupdate" and "port upgrade outdated" (I'm a stickler for 
keeping up to date); it failed two weeks in a row with the above error, 
but worked when I repeated it the next day.

-- Dave