Seems good for doing DNS Redundancy or running something like a PiHole server. Thanks!

If I had to do it again, and I didn't care, I'd probably just get a KS-1 and stick shit on that, then use my registrars' free DNS service. The /32 and /128 lockdown kills me, though.

I've been trying to move away from DNS hosting, but my intent was not to cut the service off. However, the current issue is listed and will be updated here: https://mxstatus.co

I thought MXR disabled DNS support?

(Quote)

Goes without saying, ensure you have proper forward/reverse DNS records set up and matching, as well as SPF records. Some will suggest you also DKIM and DMARC, but personally I don't bother with those

(Quote)

* Host your DNS with the company that hosts your website.

Shit happens. Use good DNS services(read as:your own) if you host anything of importance as this happens to the best. Even buyshared fucked up a while ago. Monitor detected within a minute, DNS change

I'm the realistic type who can put together why this block was put into place and that you are an extreme edge-case of a user who is performing forward DNS lookups. You wanna run that service? Go run

need 1 IP per machine (and don't need reverse dns). A reliable network is probably reasonably important however. Intermittent packet loss is annoying for our application, so providers that experience

Yes, that would definitely allow people that want to CPU-mine XMR or other cryptocurrencies on their Vultr servers but doesn't help in my case as my Vultr instances do resolve DNS records themself. I'

Sorry, I wasn't quite clear what your specific use-case was. I was assuming you could run your own caching resolver elsewhere, and encrypt DNS between that resolver and your Vultr VMs.

* Shows information about the wifi connection (external IP, signal strength, download and upload speed, subnetmask, gateway, DNS).

calling bullshit here because blocking this by DNS only shifts the problem instead of actually solving it: One could still hardcode minexmr.com servers' IP addresses into their stratum clients for mi

It clearly sounds like one support tech though you were unable to resolve a domain on your server (hence the mention of port 53 inbound) and another staff member had no idea they had DNS block lists.

This agreement covers QuadraNet’s internal network infrastructure, including connectivity to transit providers, routers, and switches. This SLA does not cover cabling faults and/or failures, service i

* 2017-10-20 20:21:59 After debugging, I told them that I noticed that DNS requests that have "minexmr.com." in the name (anywhere in the domain, even "test.minexmr.com.goog

It's bad for anything DNS resolver related - we noticed this when our users complained about it.

Just tried to multiple dns servers from both NJ & Miami with the same results. As far as I can tell from a quick glance there's nothing in the ToS/AUP about traffic manipulation. Very worrying