Thanks but DNS is not real time fail over solution:

What you want to achieve is not that simple and I don't think providers will help you or teach you how to do that for free. The simplest solution is to just use a failover dns solution which does heal

IMO BuyVM's anycast is meant for more specific use cases, like DNS or some CDN setup where GeoDNS routing, etc. isn't an option.

(Quote)

(Quote)

(Quote)

Maybe it will be better to write that you block port 25 and do NOT allow reverse dns with all VPS packages.

That's why DNS exists (Image)

Yes correct. It is DNS64 and NAT64. works fine for any other OS

@kevertje said:

NAT64 is not enough for that you also need to use a DNS64 DNS server to make it work. Or 464XLAT for stuff that doesn't use DNS at all.

(Quote)

(Quote)

(Quote)

Just to confirm, I will set my server DNS AAAA IPv6 record as:

(Quote)

So is my IPv6 XXXX:4f8:c17:1e0f::1/64? Is that I should use as AAAA DNS record?

(Quote)

First time setting up an AAAA DNS record for my server IPv6 hostname. Sorry for asking this, but I’m really a newbie when concerning IPv6.

This is decide at clients’s side to prioritize IPv6, unless ISPs actively practice DNS hijacking