Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ppIg8-0004FF-PZ for pgsql-admin@arkaria.postgresql.org; Thu, 20 Apr 2023 01:01:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ppIg7-0002tf-67 for pgsql-admin@arkaria.postgresql.org; Thu, 20 Apr 2023 01:01:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ppIg6-0002rz-QN for pgsql-admin@lists.postgresql.org; Thu, 20 Apr 2023 01:01:38 +0000 Received: from mail-qt1-x82a.google.com ([2607:f8b0:4864:20::82a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ppIg0-000mtI-4I for pgsql-admin@lists.postgresql.org; Thu, 20 Apr 2023 01:01:37 +0000 Received: by mail-qt1-x82a.google.com with SMTP id d75a77b69052e-3ef3298307eso596881cf.3 for ; Wed, 19 Apr 2023 18:01:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681952491; x=1684544491; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=iPX2QOu3rRSZE9Nn+CfxDQVXcyy6zYCthaKWyS4JVb4=; b=lnhD7Md1rg0VtF37GP8/GmWwYFiaD0Hc/OzmPeHMjia40SnmIlRFPlcVpmaCy0EVyh Ob71Oqo0hKsr/hN3XBfKzRkjbNgX/hCqoNcSzC5Qaw08nMASh/16io2gBA2I2Wo/y4Ke FYJhnBUMNgO5DSfsaKIVbthWEpdH9YOegbo0Y3dE6A5ZppwjyD8JWuNitZSB6hN8LDg7 DHEQEMswFlTVSgGa0ScZg7USi/41OqFfgehaNB+fNsYmI6QXX46EYgYlM2O/X7UAceCk pA+u3Yq6r6L6y12pyapgkOeXx25PW1iuMiCsoeVQS6MB4aqIkpVz7BVKHZQnW+a8KK0X Kv9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681952491; x=1684544491; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=iPX2QOu3rRSZE9Nn+CfxDQVXcyy6zYCthaKWyS4JVb4=; b=JMEUcxVaAhF6d0sn09WozqOuOukkHaBZl7AdV4dRZky4x1iS8pJlbe3Xa2k51I6DEM ZkIenPOkpqKlDONBX3WtS6p8jqp+nZJ3EUGrbkDeOAqO/mEhKFQPWDj45jqIWhCdsDck n7JxE0kbrelEazeMvq2a3y92cSaJdxtCa28RtJmjcppI3Q2yit/T6ugLfRFN/5BfvVqD gFuRFCuPfwGArW/AJ0J/FHWECQetB9jEFjFKxxzeJiZ97rXvTH5XZNQYe7yN8QmFvl/H aMCkZ6oZ3PibFMJY+bGlAUC987luD0BYmVqKjWY8/RFzAdIQIEGwfAR4v9PUEe3zTUFD 8+Gw== X-Gm-Message-State: AAQBX9cKIIDNJH4cUPo7WuLrNQVPlKmFU/zbqI4UNOkCoMS/g+g7ZKAa 1yhkmFpc3bXrp51j+h+QSKY= X-Google-Smtp-Source: AKy350YRLg/7IRmtUQx0F4zyLp9GZrh7KpUFCsV6ZN+e1tkqb5PCO6oTTJtbrLV79Fn9oFtoosMnDQ== X-Received: by 2002:ac8:5d91:0:b0:3e6:454f:9a89 with SMTP id d17-20020ac85d91000000b003e6454f9a89mr710437qtx.14.1681952491125; Wed, 19 Apr 2023 18:01:31 -0700 (PDT) Received: from smtpclient.apple ([209.33.119.14]) by smtp.gmail.com with ESMTPSA id x5-20020ac87ec5000000b003e014845d9esm139554qtj.74.2023.04.19.18.01.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Apr 2023 18:01:30 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: John Scalia Mime-Version: 1.0 (1.0) Subject: Re: PgAdmin cannot locate my server Date: Wed, 19 Apr 2023 21:01:19 -0400 Message-Id: <75888106-1D93-4E7D-BC84-F490A3F92F52@gmail.com> References: Cc: Pgsql-admin In-Reply-To: To: "Wetmore, Matthew (CTR)" X-Mailer: iPad Mail (20D67) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk You are correct this problem was from windows and PgAdmin 4v6. At least that= =E2=80=99s 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 t= he db. Then I reconfigured PgAdmin to connect using the db=E2=80=99s IP addr= ess. That all went quite well and I connected with the db. For grins, I reco= nfigured PgAdmin back to the db=E2=80=99s FQDN, and had it try a reconnectio= n. Strangely enough it did connect and there were no issues., but the only c= hange 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) wrote: >=20 > =EF=BB=BFI'm assuming this is windows. =20 > I ran into this when PGAdmin is fine with qualified DNS hostname, but the p= g_pass file couldn't resolve and needed dotted quad. >=20 > The corporate-world structure of windows networking and permissions is a m= ystery to me... >=20 > Just use the dotted quad and move along! lol >=20 > =46rom cmd:=20 >=20 > nslookup < ple.mydomain.com > >=20 > pg_pass.conf > :::: >=20 >=20 > -----Original Message----- > From: John Scalia =20 > Sent: Monday, April 17, 2023 12:45 PM > To: Pgsql-admin > Subject: [EXTERNAL] PgAdmin cannot locate my server >=20 > I=E2=80=99ve got something really weird going on. My laptop can easily fin= d my PLE production (production like environment) using a normal nslookup, b= ut PgAdmin emits an error saying could not translate host name =E2=80=9Cple.= mydomain.com=E2=80=9D host to address: Unknown host >=20 > So where is PgAdmin looking regarding DNS entries? I would think that if t= he laptop can find it, that any app running on it should be able to do so. > =E2=80=94 > Jay >=20 > Sent from my iPad6 >=20