Does anybody else use outbound routing by DNS name? This seems like such a great way to balance traffic. Unfortunately, the way it is currently implemented does not work. Very rarely does a reverse lookup yield the actual domain name of the website that you are talking to.
youtube.com resolves by forward lookup to 216.58.193.206. A reverse lookup of 216.58.193.206 yields the name 206.193.58.216.in-addr.arpa with an alias of lax02s23-in-f206.1e100.net. So, if I wanted to do a simple routing for all youtube traffic; I would have to set up individual outbound policies for every possible network that has youtube servers in it. And then keep it all up to date and current as the youtube pointers move around.
This is a huge deficiency. Maybe it worked 10-15 years ago when servers only ran one website, but in the cloud based world with dispersed datacenters and DNS trickery happening everywhere - - it doesn’t work. Should I submit a feature request to spend some time on engineering a forward resolution based approach?