Bug 1327555

Summary: dnssec-trigger breaks reverse lookup from VPN connection
Product: [Fedora] Fedora Reporter: Tomáš Hozza <thozza>
Component: dnssec-triggerAssignee: Paul Wouters <pwouters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 28CC: pj.pandit, pwouters, thozza
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 19:37:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tomáš Hozza 2016-04-15 11:32:19 UTC
Description of problem:
dnssec-trigger by default configures forward zones for private address ranges in Unbound. As forwarders it uses DNS resolvers of the default connection from NM.

When I connect to VPN, the connection provides DNS resolvers and domain, as well as subnet. NM adds default route for the subnet and dnssec-trigger configures Unbound with forward zone to the VPN provided domain. However the forward zones for reverse zones of private address ranges are still configured  with the resolvers from the default connection.

As a result Unbound uses wrong set of resolvers when doing a reverse lookup for some IP address and the resolution fails.

dnssec-trigger should either prefer the VPN provided resolvers for reverse forward zones. Other possibility is to do it in a "smart" way and use resolvers from a connection based on the subnet of the connection.


Version-Release number of selected component (if applicable):
latest

How reproducible:
always

Steps to Reproduce:
1. have some active connection and make sure dnssec-trigger is configured to add forward zones for private address ranges.
2. connect to a VPN, which uses private address subnet
3. do a reverse query for IP from the VPN subnet

Actual results:
reverse query is forwarded to the resolver from default connection

Expected results:
reverse query is forwarded to the resolver from VPN

Additional info:

Comment 1 Paul Wouters 2016-04-15 18:17:37 UTC
This is a problem with the IKEv1 specification for domains. You can only specify one. With IKEv2 we are fixing this with a protocol change:

https://tools.ietf.org/html/draft-pauly-ipsecme-split-dns-00

With this implemented, libreswan will be able to send/receive multiple domains to be forwarded to the nameserver over the VPN.

Comment 2 Tomáš Hozza 2016-04-18 07:05:49 UTC
Paul, it seems to me that you didn't understand my description. This is an issue with dnssec-trigger and the way it configures Unbound. It has nothing to do with multiple domains and also it has nothing to do with libreswan, as I don't use libreswan. U use OpenVPN and VPNC.

Please keep this bug assigned to dnssec-trigger, as this is mostly for us to not forget and fix this eventually.

Comment 3 Jan Kurik 2016-07-26 04:57:51 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 4 Fedora End Of Life 2017-11-16 19:38:30 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:50:07 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Fedora End Of Life 2018-02-20 15:32:46 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 7 Ben Cotton 2019-05-02 22:03:54 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2019-05-28 19:37:38 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.