14 Mar
2018
14 Mar
'18
19:08
On Wednesday, 14 March 2018 19:02:34 GMT Philip Tait wrote:
I had this happen to me a while back. As I recall, the issue was that /etc/resolv.conf only contained an IPv6 address for a nameserver. Adding another line with the IPv4 address of the router fixed it for me.
Philip
Thank you for your reply Philip. Fabian's suggestion worked for me, but I suspect your advice would have worked too as it did indeed seem like a name resolution issue specifically. Kind regards, Huw