(Quote)

* FlushDNS

(Quote)

Their network problems are the same, similar to EvosHosting which experiences a bad network gateway that even fails, high ping, sometimes fine, connecting to the DNS server is unstable.

Joke aside... @AvaHosting do yourself a favor, reenable the customer, improve your templates, DNS settings and maybe change your internal policy howto handle abuses ( if ever such an abuse report exis

(Quote)

(Quote)

(Quote)

First, these fancy, weirded names I set as the core hostnames and have a dns pointing to the main ip.

So the wildcard DNS is indeed gone now

Customer has ava.hosting in resolv.conf, ava.hosting has wildcard dns for this domain.

488.87 Mbit/s 92.004 ms Germany, Berlin (DNS:NET) 155.32 Mbit/s 440.40 Mbit/s 114.208 ms Spain, Madrid (MasMovil) 164.52 Mbit/s 464.33 Mbit/s 100.707 ms Italy, Rome (Unidata

If the customer installed from template and the template contains a resolvconf like this, it's entirely the provider's fault, for having such a template along with the wildcard DNS.

"I'm using 1.1.1.1 DNS. Do you mean that my VPS sent thousands of "GET /connecttest.txt" requests to your mail host (176.xxx.xxx.xxx) instead of Microsoft or Akamai CDN edge

Wildcard DNS records rocks! (Image)

(so probably the client just thinks it is now in the ava.hosting domain and automatically appends that to DNS queries, and then the web server there responds with a redirect and the client just follow

* I'm using 1.1.1.1 DNS. Do you mean that my VPS sent thousands of "GET /connecttest.txt" requests to your mail host (176.xxx.xxx.xxx) instead of Microsoft or Akamai CDN edge server?

NCSI sends a DNS request to resolve the address of the www.msftconnecttest.com FQDN.

(Quote)

(Quote)