I've just installed "Tara" LMDE which I like a lot.

I've fudged a VPN using TCP and 443 port on ISP router - Technicolor DJA0230. I can't bridge it without losing internet access and 4G capability. I've tried to setup VPN on my router running latest dd-wrt firmware, but have been encountering a problem probably relating to system.d that I have no knowledge of whatsover. The resolv.conf file has 127.0.0.53 which I'm guessing is something to do with DNS.

I think the problem is getting my VPN providers software client and managing DNS resolution. I can connect to the internet when I piggyback it onto ISP router but I can't resolve DNS it seems. The ISP's router has firmwared DNS settings that can't be changed.

Can someone help with system.d and DNS resolution? Or whatever is going on?

There is no such thing as "Tara" LMDE. The current version of LMDE, LMDE 2, is "Betsy" and the forthcoming version, LMDE 3, will no doubt have a different name.

Is this some form of beta you're playing with?

https://blog.linuxmint.com/?p=3598

It is this. Not a Beta version. Same as what you are using. I got the LMDE wrong. I wanted to make it clear it was the Debian Mint version, not the Ubuntu one.

That is the Ubuntu-based one though. LMDE is the Debian-based flavour.

Is that the only entry in /etc/resolv.conf? That's a localhost IP...are you running a DNS server?

Add the DNS server IP(s) of your ISP and/or Google's DNS server at 8.8.8.8 to /etc/resolv.conf

Given you are not running your own DNS server, system.d should have nothing to do with DNS resolution issues.

Sorry Hydurga,

A lot of stuff to deal with at the moment! Telstra has had some devastating outages, NBN being rolled out in street, neighbourhood hacker trying to do DOS all the time, ? VPNfilter, ISP router and my tablet sizzled on the same day etc.

Yes 127.0.0.53 was the only entry.

It could be the neighbourhood hacker has hacked router/s. Someone was definitely hacking desktop again. Long story. At the moment all seems to be well as I'm using a VPN for my wireless desktop and an eopl connection only.

One entry in resolv.conf had said something about system.d doing resolving issues now, which is why I'm so confused. I know nothing about system.d. Can't post as I wiped partitions and reinstalled due to hacking.

I seem to have DNS issues if I factory reset routers. It could be something to do with ISP's firmwaring DNS to their routers. But with so much going on at the same time, it is hard to sort things out. My ISP has sorted it out for me a few times though and I can resolve DNS again.

Thanks both of you for your reply, I'll leave it for time being.

I will try adding ISP and Googles DNS entries in resolv.conf. This is it's current content

# resolv.conf(5) file generated byTorGuard
nameserver 10.9.0.1
nameserver 10.8.0.1

# ORIGINAL CONTENT:
# # Generated by NetworkManager
# search gateway
# nameserver 127.0.0.53

Unless for some reason Tara loads a DNS server I have not gone to the trouble of setting one up for my now sole device.

Thanks

PS. Wireless is definitely history around here due to the neighbourhood vindictive destructive hacker.