Policy based routing - TLD not GeoIP

[pawlisko]

Hi,

Maybe this is a weird question, but I want to do it my way.

I am based in country X, and I have VPNs to countries Y and Z. They are based now on GeoIP, but from time to time, there is a problem. I want to appear from country Y via VPN to Y, but some of the services for country Y are using servers in country Z which forces traffic via VPN to Z, based on that (my IP appears as Z using GeoIP) I am denided service as service say that I am in country Z.

Having said that, and I do understand the routing and performance factors of my ask, is there a way to do policy routing using TLDs as a differentiator, not GeoIP?

Thanks

[pawlisko]

I would implement this on a cross of DNS and routing. Basically DNS resolves name, if TLD is equal to VPN rule, then those IPs are put in the routing table for VPN routing. Also it would have a timer based on DNS record’s TTL to purge those IPs from the routing table when DNS would need to re-resolve them.