Bug 985415

Summary: openvpn does not resolve the remote fqdn right after reboot
Product: [Fedora] Fedora EPEL Reporter: Dalibor Pospíšil <dapospis>
Component: openvpnAssignee: Steven Pritchard <steve>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: bjoern, dazo, gwync, huzaifas, steve
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-16 11:02:50 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:
Embargoed:

Description Dalibor Pospíšil 2013-07-17 12:47:16 UTC 
Description of problem:
openvpn does not resolve the remote fqdn right after reboot and announce if in  logs.

After service is restarted in resolves ok. It seems like the name resolution occurs earlier then the DNS is set and it does not try it again or what.


Version-Release number of selected component (if applicable):
openvpn-2.3.1-3.el6.x86_64

How reproducible:
always on my machine

Steps to Reproduce:
1. create a vpn config for connection at the start of service
2. reboot
3. check /var/log/messages

Actual results:
/var/log/messages:
Jul 17 14:37:12 sopos openvpn[5039]: RESOLVE: Cannot resolve host address: <host>: Temporary failure in name resolution
Jul 17 14:37:17 sopos openvpn[5039]: RESOLVE: Cannot resolve host address: <host>: Temporary failure in name resolution
Jul 17 14:37:22 sopos openvpn[5039]: RESOLVE: Cannot resolve host address: <host>: Temporary failure in name resolution
...
every 5s appears new message


Expected results:
only few unsuccessful attempts
Comment 1 Björn Ruberg 2013-12-19 11:16:45 UTC 
I think this is a duplicate of #966281
Comment 2 David Sommerseth 2018-02-16 11:02:50 UTC 

*** This bug has been marked as a duplicate of bug 966281 ***