Re: BUG #15655: local machines pushed openvpn dns issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: aaffee(at)follett(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15655: local machines pushed openvpn dns issue
Date: 2019-02-25 22:14:12
Message-ID: 6491.1551132852@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> The psql command line for MacOS looks to external DNS resolution first.
> Once it fails, it then looks to the local machines DNS to resolve hostname.

Neither psql nor libpq (or indeed anything in PG) contain their own
DNS resolution code. It's just using whatever behavior the local libc
provides for that.

Apple's libraries do indeed have some nonstandard DNS resolution behavior,
though. Some quick poking around here suggests that "scutil --dns" might
help you investigate how that's configured on your machine.

Also worth noting is that the PG community at large has no idea what AWS
may have done to versions that they provide; if this isn't a purely
stock psql, you should probably be asking AWS about it.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-02-25 22:30:32 Re: BUG #15655: local machines pushed openvpn dns issue
Previous Message Rossiter, Russell D. 2019-02-25 21:55:41 Kerberos bug in pgadmin4.2