Thanks for the quick reply. Here’s some details on how we have things configured. We are using RHEL 7.3, the DNS names below have been changed to protect the innocent or not so innocent depending on your point of view. If I do a nslookup on the database host against the following CNAME some-cname-host.example.com I get: Server: 10.97.40.215 Address: 10.97.40.215#53 some-cname-host.example.com canonical name = canonical-host-name.example.com. Name: Address: 10.65.160.213 Server: 10.97.40.215 Address: 10.97.40.215#53 213.160.65.10.in-addr.arpa name = canonical-host-name.example.com. In our pg_hba.conf I have a line: hostssl replication streaming_user_name some-cname-host.example.com But when I try to connect as the streaming_user_name with the following command, I get the following error (postgresql_hostname is the host where I ran the nslookups above): bash-4.2$ psql -U streaming_user_name -h postgresql_hostname -c "IDENTIFY_SYSTEM" replication=1 psql: FATAL: no pg_hba.conf entry for replication connection from host "10.65.160.213", user "streaming_user_name", SSL on FATAL: no pg_hba.conf entry for replication connection from host "10.65.160.213", user "streaming_user_name", SSL off So I am not sure what I would need to fix or add on the database host to allow it to resolve the CNAME in way the postgres instance could use it and have it pass the validation rules from the documentation. Am I missing something in the DNS configurations?
|
