okay it wasn't DNS, the whole thing broke which lead to DNS not being reachable

@ruhrscholz but it's always DNS

@crablab I don't even know what's wrong, but rebooting everything has made things worse

@ruhrscholz :(
What did you reboot? If it's a name resolution issue and you've just flushed the cache...

@crablab Local router and virtual remote router. Doesn't seem to be DNS though as I can't reach anything when going through the tunnel anymore

@ruhrscholz Oh dear, that sounds worse. I have less experience than you here! I'm interested in what the issue turns out to be though

@crablab I have no clue what I'm doing as well. IPv4 works again, the virtual cloud router had for some reason dropped all the iptables/nftables rules, including the IPv4 NAT. As for IPv6 it's probably the same issue, just have to figure out the rules I set earlier

@ruhrscholz If it's dropped all the tables, how do you get remote access without a management interface? 👀

@crablab the VPS is publicly reachable by default via port 22, the iptables rules are only there for NATing the outgoing IPv4 traffic