Dear Niibe-san, Thanks for your response!
While trying on Flets network seems fine (sometimes, not always), I feel it always get failed on LTE networks (Pocket Wifi). So seems it's a network environment dependent issue. Here's my result by LTE networks (Pocket Wifi): $ dirmngr --server --homedir=/run/user/1000/test dirmngr[25354]: error opening '/run/user/1000/test/dirmngr_ldapservers.conf': No such file or directory dirmngr[25354.0]: permanently loaded certificates: 0 dirmngr[25354.0]: runtime cached certificates: 0 # Home: /run/user/1000/test # Config: [none] OK Dirmngr 2.1.18 at your service KS_GET -- 0x6C6ACD6417B3ACB1 dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'sks.spodhuis.org' dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'oteiza.siccegge.de' S PROGRESS tick ? 0 0 dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'bone.digitalis.org' dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'prod00.keyserver.dca.witopia.net' dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'gpg.NebrWesleyan.edu' S PROGRESS tick ? 0 0 dirmngr[25354.0]: resolve_dns_addr failed while checking 'hkps.pool.sks-keyservers.net': No name dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'hufu.ki.iif.hu' dirmngr[25354.0]: resolve_dns_addr failed while checking 'hkps.pool.sks-keyservers.net': Server indicated a failure dirmngr[25354.0]: resolve_dns_addr failed while checking 'hkps.pool.sks-keyservers.net': Not found dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'bone.digitalis.org' [already known] dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'ip-209-135-211-141.ragingwire.net' S PROGRESS tick ? 0 0 dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'hufu.ki.iif.hu' [already known] dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'gpg.NebrWesleyan.edu' [already known] dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'sks.spodhuis.org' [already known] dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'oteiza.siccegge.de' [already known] S PROGRESS tick ? 0 0 dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'ams.sks.heypete.com' dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'host-37-191-238-78.lynet.no' dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'cryptonomicon.mit.edu' dirmngr[25354.0]: resolving 'ip-209-135-211-141.ragingwire.net' failed: No name dirmngr[25354.0]: can't connect to 'ip-209-135-211-141.ragingwire.net': host not found dirmngr[25354.0]: error connecting to 'https://ip-209-135-211-141.ragingwire.net:443': No name dirmngr[25354.0]: command 'KS_GET' failed: No name ERR 167772380 No name <Dirmngr> Hope this test helps. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
