I’m having what I interpret as DNS name resolution issues under FreeNAS 11.1 (based on FreeBSD 11.1-STABLE), with both rclone v1.38 (which comes already installed on FreeNAS) and v1.40 (which I downloaded from the rclone web repo and installed myself).
The problem is somewhat intermitent, but when it manifests itself, all rclone commands (not only the
lsd shown below) fail like this:
rclone lsd MYGOOGLEDRIVE: 2018/04/06 12:03:35 Failed to create file system for "MYGOOGLEDRIVE:": couldn't read info about Drive: Get https://www.googleapis.com/drive/v2/about?alt=json: Post https://accounts.google.com/o/oauth2/token: dial tcp: lookup accounts.google.com on 172.20.25.99:53: read udp 172.20.25.99:19427->172.20.25.99:53: i/o timeout
172.20.25.99 is the internal DNS server, which works perfectly well with everything else, to whit:
host accounts.google.com 172.20.25.99 Using domain server: Name: 172.20.25.99 Address: 172.20.25.99#53 Aliases: accounts.google.com has address 184.108.40.206 accounts.google.com has IPv6 address 2800:3f0:4001:809::200d accounts.google.com mail is handled by 10 alt1.gmr-smtp-in.l.google.com. accounts.google.com mail is handled by 5 gmr-smtp-in.l.google.com. accounts.google.com mail is handled by 30 alt3.gmr-smtp-in.l.google.com. accounts.google.com mail is handled by 40 alt4.gmr-smtp-in.l.google.com. accounts.google.com mail is handled by 20 alt2.gmr-smtp-in.l.google.com.
Moreover, demonstrating that the problem is indeed DNS name resolution, as soon as I add
220.127.116.11 accounts.google.com plus whatever rclone complains next www.googleapis.com, etc) to the machine’s
/etc/hosts file, rclone then works perfectly.
So, am I missing anything? Is this an rclone bug or what?