BUG #8172: entering the hostname in the address column in pg_hba.conf doesn't work as it should

From: tudorbarascu(at)yahoo(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #8172: entering the hostname in the address column in pg_hba.conf doesn't work as it should
Date: 2013-05-21 07:41:33
Message-ID: E1UehCP-0007N2-KX@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 8172
Logged by: Barascu Tudor
Email address: tudorbarascu(at)yahoo(dot)com
PostgreSQL version: 9.2.4
Operating system: Centos 6.4 kernel 2.6.32-358.6.2.el6.x86_64
Description:

In pg_hba.conf I have the following setup:
host all all laptop md5

Although the hostname gets resolved by the system (LAN DNS server) I still
get the no pg_hba.conf entry error.
If I enter the hostname and ip in the hosts file all works well.
I get the following error: (it seems the host name gets resolved but after
the deny)

2013-05-21 10:26:12 EEST:192.168.1.6(51513):sde(at)gisdb:[1997]: FATAL: 28000:
no pg_hba.conf entry for host "192.168.1.6", user "sde", database "gisdb",
SSL off
2013-05-21 10:26:12 EEST:192.168.1.6(51513):sde(at)gisdb:[1997]: DETAIL:
Client IP address resolved to "192.168.1.6", forward lookup not checked.
2013-05-21 10:26:12 EEST:192.168.1.6(51513):sde(at)gisdb:[1997]: LOCATION:
ClientAuthentication, auth.c:479

Thank you,
Tudor

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message fburgess 2013-05-21 20:54:08 Very slow inner join query unacceptable latency
Previous Message Andrzej Cedro 2013-05-21 06:54:09 Re: BUG #7659: LDAP auth does not search the subtree