Skip site navigation (1) Skip section navigation (2)

Re: Why don't we allow DNS names in pg_hba.conf?

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Larry Rosenman <lrosenman(at)pervasive(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br>, Jim Nasby <jnasby(at)pervasive(dot)com>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why don't we allow DNS names in pg_hba.conf?
Date: 2006-01-03 22:31:40
Message-ID: 20060103223140.GA4407@wolff.to (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Jan 03, 2006 at 12:08:46 -0600,
  Larry Rosenman <lrosenman(at)pervasive(dot)com> wrote:
> The issue is folks that DON'T set reverse DNS, I.E. have generic rDNS
> set on their IP's.
> 
> I've seen (in my ISP days, and on my mailserver) LOTS of folks that
> can't/won't update
> Their rDNS, even though it's a STATICLY assigned address. 
> 
> And, as an example, my house IP changes when the PPPoE moves, and I have
> a DynDns.org
> Hostname that changes to support that, as well as a CNAME out of my
> domain to 
> Point to it. 

Business class (or Speakeasy) broadband connections will generally allow
you to have custom PTR records for static IP addresses. When using broadband
for sheep, the ssh tunnel idea is probably a better solution.

In response to

pgsql-hackers by date

Next:From: Larry RosenmanDate: 2006-01-03 22:33:09
Subject: Re: Why don't we allow DNS names in pg_hba.conf?
Previous:From: Hannu KrosingDate: 2006-01-03 21:42:53
Subject: Re: Stats collector performance improvement

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group