Works for me :) root@rel56[~] echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/
root@rel56[~] pkg_info -Q mosh mosh-1.2.4p1 root@rel56[~] dig ftp.nluug.nl ; <<>> DiG 9.4.2-P2 <<>> ftp.nluug.nl ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26971 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ftp.nluug.nl. IN A ;; ANSWER SECTION: ftp.nluug.nl. 63662 IN A 192.87.102.43 ftp.nluug.nl. 63662 IN A 192.87.102.42 ;; Query time: 2 msec ;; SERVER: 192.168.222.10#53(192.168.222.10) ;; WHEN: Fri Nov 21 04:01:08 2014 ;; MSG SIZE rcvd: 62 On Fri, Nov 21, 2014 at 3:13 AM, John Smith <hufflep...@bsdmail.com> wrote: > > > > Sent: Thursday, November 20, 2014 at 8:06 PM > From: "John Smith" <hufflep...@bsdmail.com> > To: misc@openbsd.org > Subject: No address associated with PKG_PATH mirror > Hello, I get the following error when using any of the pkg_* commands:$ > echo $PKG_PATH > http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ $ pkg_info -Q > mosh > Error from > http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] > ftp: ftp.nluug.nl: no address associated with namehttp:// > ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ > is empty This seems to occur with any mirror I choose. I am able to > access the directory via a web browser. Examining the logs in real-time > with tcpdump doesn't reveal any blocks. Also, there are no errors > written to /var/log/messages. Any ideas? Thanks > > > (I apologize for the formatting. Here is the same message in plain text:) > > I get the following error when using any of the pkg_* commands: > > $ echo $PKG_PATH > http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ > > $ pkg_info -Q mosh > Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ > [http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] > ftp: ftp.nluug.nl: no address associated with name > http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ is empty > > This seems to occur with any mirror I choose. I am able to > access the directory via a web browser. Examining the logs in real-time > with tcpdump doesn't reveal any blocks. Also, there are no errors > written to /var/log/messages. Any ideas? > > Thanks