Project

General

Profile

Bug #8902

HAproxy package not use custom DNS for lookup on apply new config

Added by DRago_Angel [InV@DER] 10 months ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
haproxy
Target version:
-
Start date:
09/16/2018
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:
All

Description

Package Version:
haproxy-devel net 0.59_9

Package Dependencies:
haproxy-devel-1.8.13 

cat /etc/version
2.4.3-RELEASE

cat /etc/version.buildtime
Thu May 10 15:02:52 CDT 2018

How to reproduce:
1. Install and configure HAproxy for simple any one frontend/backend
2. Configure DNS on HAproxy to use non pfSense system DNS
3. Change backend IP to DNS (example.internal) record that can't be resolved by pfSense system DNS but can by HAproxy custom DNS
4. Try apply new configuration in HAproxy package - you will se error that DNS record for backend can't be resolved

History

#1 Updated by Pi Ba 10 months ago

Hmm, i suppose your right.

You could add below to the 'global advanced pass thru', that should solve the issue.

defaults
    # never fail on address resolution
    default-server init-addr last,libc,none

Not sure yet if the above should get added automatically when configuring dns-resolvers..

#2 Updated by DRago_Angel [InV@DER] 10 months ago

Pi Ba wrote:

Hmm, i suppose your right.

You could add below to the 'global advanced pass thru', that should solve the issue.
[...]

Not sure yet if the above should get added automatically when configuring dns-resolvers..

Hi Pi Ba, thank you for yours help. This really fix situation, maybe you can add checkbox that add this line to default section.
Like:
"Global DNS resolvers for haproxy table"
"DNS servers: dns1 ip, dns2 ip"
"Check this option to not fail if you have resolving issues when you try resolve internal DNS records"
And add description that describe what this option adding to config.

Also available in: Atom PDF