(Quote)

As long as you're sending mail from all of these domains, then yes. You'll have to add each domain and update the TXT and MX records with your DNS hoster accordingly to point to mailgun servers. When

As it is not just a single AS (Kaspersky is not on VK) i suspect single IP bans - DNS censorship is unlikely as no one uses his ISPs DNS anyway (so need DNS interception and so on...).

I wonder how they block it? Just dropped VK and others from DNS or drop all routes to VK AS? I doubt that UA can do some sophisticated and fancy DPI magic like China

I'd be interested to see how it'll be implemented - Is it directed for eyeball ISPs to block clients (DNS blocking or similar)? Or will all ISPs be forced to drop AS47542 connectivity?

[shell@router.***.com] > tool traceroute lg.x4b.net use-dns=yes count=10

VK resolves on ISP DNS as well:

It will go to inbox if its DNS and content are valid.

[shell@router.***.com] > tool traceroute lg.x4b.net use-dns=yes count=10

The internal hops are typical for 4G over long distance to a central core and similar, useless and weird with no hostnames set but yea. If you use other DNS you might want to trace with the ISPs DNS e

* Reverse DNS

**All Unmanaged vps services include the following:**24/7 Fast, helpful supportInstant SetupDDoS Protection (DDoS Detection And Auto-Mitigation)-upto 3gbpsCustom Reverse DNSVNC Console Enterprise-clas

@raindog308 I'm not forced to use their DNS. I just can't open port 53 from outside to inside so I can't create a DNS server from the inside but I can connect to others. Actually I'm using Google's DN

(Quote)

I'd consider an ISP forcing me to use only their DNS server to be a deal breaker...you need to either find a new ISP or VPN out.

* Free reverse DNS management

(Quote)

even if they use the dns , most of them are resellers and using whmcs so they whitelisted the server ip , the customers must know that the ip have been changed , or know that they have been forced to

Oh inbound. Yeah then you can use a DNS only install elsewhere and make sure that's your nameserver.

They didn't block 53 completely, probably just force you to use their DNS servers. Set their resolvers up on the server and you should be set. Should be easily found in your router config.