You are correct this problem was from windows and PgAdmin 4v6. At least that’s what my company calls it. The database was an AWS RDS version 12.4. The eventual fix was even stranger. As an experiment I ran nslookup against the db. Then I reconfigured PgAdmin to connect using the db’s IP address. That all went quite well and I connected with the db. For grins, I reconfigured PgAdmin back to the db’s FQDN, and had it try a reconnection. Strangely enough it did connect and there were no issues., but the only change here was the fact that I first connected using the IP adress. Sent from my iPad > On Apr 19, 2023, at 6:04 PM, Wetmore, Matthew (CTR) <Matthew.Wetmore@xxxxxxxxxxxxxxxxxxx> wrote: > > I'm assuming this is windows. > I ran into this when PGAdmin is fine with qualified DNS hostname, but the pg_pass file couldn't resolve and needed dotted quad. > > The corporate-world structure of windows networking and permissions is a mystery to me... > > Just use the dotted quad and move along! lol > > From cmd: > > nslookup < ple.mydomain.com > > > pg_pass.conf > <IP.IP.IP.IP>:<port>:<db>:<User>:<PASSWORD> > > > -----Original Message----- > From: John Scalia <jayknowsunix@xxxxxxxxx> > Sent: Monday, April 17, 2023 12:45 PM > To: Pgsql-admin <pgsql-admin@xxxxxxxxxxxxxxxxxxxx> > Subject: [EXTERNAL] PgAdmin cannot locate my server > > I’ve got something really weird going on. My laptop can easily find my PLE production (production like environment) using a normal nslookup, but PgAdmin emits an error saying could not translate host name “ple.mydomain.com” host to address: Unknown host > > So where is PgAdmin looking regarding DNS entries? I would think that if the laptop can find it, that any app running on it should be able to do so. > — > Jay > > Sent from my iPad6 >
