<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[SOLVED] Is there a way to use FQDN for OpenVPN client instead of IP?]]></title><description><![CDATA[<p dir="auto">Let's say I want to establish a VPN client tunnel to <strong>us-newyorkcity.privateinternetaccess.com</strong>, which resolves to:</p>
<p dir="auto">209.95.50.15<br />
209.95.50.18<br />
209.95.50.19<br />
107.182.231.28<br />
209.95.50.102<br />
209.95.50.103<br />
173.244.223.122<br />
209.95.50.129<br />
209.95.50.133<br />
209.95.50.142<br />
209.95.50.149<br />
209.95.50.162<br />
209.95.50.163</p>
<p dir="auto">among many other A records.  Assume that new A records are added and removed all the time.  I also have the DNS Resolver (unbound) to only resolve DNS out the VPN connection.  I've lately just hardcoded an IP address I've chosen at random into the client configuration, but this limits me to always connecting to one endpoint, and it may or may not go down for maintenance or suffer other issues.  Plus I want my VPN IP to change every time the tunnel is established and not limit myself to just one address, for privacy reasons.</p>
<p dir="auto">My goal is to use FQDN in the client configuration; e.g. use <strong>us-newyorkcity.privateinternetaccess.com</strong> instead of <strong>209.95.50.15</strong>, but as it currently is, since DNS resolves over the VPN tunnel (to prevent DNS leaking out over the naked WAN connection to my ISP), it will be unable to resolve and find an A record in order to connect.</p>
<p dir="auto">Are there any advanced options/settings where I can tell unbound to resolve DNS over the naked WAN <em>if and only if</em> the VPN tunnel hasn't been established yet?</p>
]]></description><link>https://forum.netgate.com/topic/119121/solved-is-there-a-way-to-use-fqdn-for-openvpn-client-instead-of-ip</link><generator>RSS for Node</generator><lastBuildDate>Tue, 06 Oct 2026 17:43:05 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/119121.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 14 Aug 2017 10:03:32 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to [SOLVED] Is there a way to use FQDN for OpenVPN client instead of IP? on Mon, 14 Aug 2017 15:13:03 GMT]]></title><description><![CDATA[<p dir="auto">But are you not worried that you will be leaking dns from pfsense when it checks for updates and package list, etc. &lt;rolleyes&gt;;)&lt;/rolleyes&gt;</p>
]]></description><link>https://forum.netgate.com/post/716004</link><guid isPermaLink="true">https://forum.netgate.com/post/716004</guid><dc:creator><![CDATA[johnpoz]]></dc:creator><pubDate>Mon, 14 Aug 2017 15:13:03 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Is there a way to use FQDN for OpenVPN client instead of IP? on Mon, 14 Aug 2017 14:47:07 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/heper">@<bdi>heper</bdi></a>:</p>
<blockquote>
<p dir="auto">You can set a different DNS server in general settings.<br />
pfsense itself will use that one. Clients behind it will use unbound</p>
</blockquote>
<p dir="auto">That was way too easy.  I overthought it.  Thanks.</p>
]]></description><link>https://forum.netgate.com/post/715998</link><guid isPermaLink="true">https://forum.netgate.com/post/715998</guid><dc:creator><![CDATA[Finger79]]></dc:creator><pubDate>Mon, 14 Aug 2017 14:47:07 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Is there a way to use FQDN for OpenVPN client instead of IP? on Mon, 14 Aug 2017 14:01:49 GMT]]></title><description><![CDATA[<p dir="auto">You can set a different DNS server in general settings.<br />
pfsense itself will use that one. Clients behind it will use unbound</p>
]]></description><link>https://forum.netgate.com/post/715991</link><guid isPermaLink="true">https://forum.netgate.com/post/715991</guid><dc:creator><![CDATA[heper]]></dc:creator><pubDate>Mon, 14 Aug 2017 14:01:49 GMT</pubDate></item></channel></rss>