Hi, Am 16.06.23 um 13:53 schrieb Brainmue:
possible solutions: * set up a firewall rule to forward connection * use a tcp proxy (nginx can do that) * check pg_bouncer best regards ThomasHello Thomas, Thank you for your quick reply. With firewall you mean an additional software, right? Because with iptables or netfilter I can't forward TCP packets based on the DNS alias name. Or is that possible? I have the same problem with nginx. I just looked in the documentation again but I can't find a way to distinguish which cluster to forward to based on the DNS alias. Do you have an example for me? We have already looked at pgbouncer and it works with that but unfortunately you have to do the authentication in pgbouncer. Which we don't like so much. Regards, Michael
You cant setup firewall rules basedon dns names. firewall rules are based on ip adresses and dns resolution happens on rule creation. I dont have an example for nginx. As I remember nginx resolves dns names only for variables. So setup a variable with your hostname and use this variable in your server definition.
best regards Thomas
Attachment:
OpenPGP_0x9794716335E9B5AF.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
