only the DNS

Lots of utility can be had from 2GB ram such as lean VPS for a static site, reverse proxy, wireguard VPN, DNS server, small API, cron jobs, monitoring, IRC/bot service, tiny database, lightweight app

ms 0.1 ms 0% ━━━━━━━━━━━━━━━╌ Google DNS (anycast) 0.9 ms 0.1 ms 0% ━━━━━━━━━━━━━━━━ Quad9 (anycast) 0.9 ms 0.0 ms 0% ━━━━━━━━━━━━━━━━ Latency under

ms 0.0 ms 0% ━━━━━━━━━━━━━━━╌ Google DNS (anycast) 1.1 ms 0.0 ms 0% ━━━━━━━━━━━━━━━╌ Quad9 (anycast) 1.1 ms 0.1 ms 0% ━━━━━━━━━━━━━━━╌ Latency under

This is exactly what DNS is for.

root@home:~# traceroute -U 66.28.0.45traceroute to 66.28.0.45 (66.28.0.45), 30 hops max, 60 byte packets 1 _gateway (147.90.234.1) 0.465 ms 0.423 ms 0.401 ms 2 69.12.96.65 (69.12.96.65) 1.935 ms

(Quote)

(Quote)

@Fourplex Can you check if you can access 66.28.0.45 and 66.28.0.61 from within the VPS? Those are the Cogent upstream DNS resolvers, but I believe they only allow access from a Cogent address space.

-Reverse DNS Support

(Quote)

(Quote)

If I go that route, I could just run another resolver on one of my existing servers that does have a clean IP and set up a DoT server on it, but latency really is a problem, and surprisingly almost al

I was imagining something like an encrypted VPN to some clean IP and routing DNS through that tunnel. SNAT at the clean IP

Does your upstream operate its own DNS resolver (just one hop from your gateway to it)?

Unfortunately, we do not have a local DNS resolver.

@Fourplex Do you have a local DNS recursive resolver on your node? Tor exits benefit significantly from that because they do not need to use a centralized upstream nameserver like Google DNS.

(Quote)

(Quote)

(Quote)