<?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[A gateway can not be assigned to DNS server which is on a directly connected network]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">I'm facing an issue while configuring a DNS forwarder.<br />
In my configuration, the upstream DNS server is also the upstream gateway.</p>
<p dir="auto">Let's say that :</p>
<ul>
<li>LAN is 192.168.0.0/24</li>
<li>WAN is 192.168.255.0/24. (private network is not a mistake, this is an interconnection to the upstream router). .253 is pfsense, .254 is the upstream router.</li>
<li>An upstream gateway is declared on WAN interface with 192.168.255.254</li>
<li>The upstream router also privide the DNS service (And I have to use it for this WAN interface.<br />
It is related to MPTCP bypass function on the upstream router. No choice)</li>
<li>(of course nat is disabled on pfsense)</li>
</ul>
<p dir="auto">So in "general config" I try to add 192.168.255.254 as DNS forwarder, and make it use the gateway (which has the same IP)</p>
<p dir="auto">It gives the following error :</p>
<pre><code>A gateway can not be assigned to DNS '192.168.255.254' server which is on a directly connected network.
</code></pre>
<p dir="auto"><strong>I can't figure out if it's a feature or a bug. What would be the point of such limitation ?</strong></p>
<p dir="auto">Please note that everything is working well if I use an online DNS like 1.1.1.1 or 8.8.8.8 except that I will have some MPTCP limitation if I can't use 192.168.255.254 instead.<br />
I'm using version 2.4.5-RELEASE-p1.</p>
<p dir="auto">Does anybody have an explanation (or a solution) ?</p>
<p dir="auto">Thanks</p>
]]></description><link>https://forum.netgate.com/topic/161012/a-gateway-can-not-be-assigned-to-dns-server-which-is-on-a-directly-connected-network</link><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Apr 2026 21:38:38 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/161012.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 18 Feb 2021 14:21:23 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to A gateway can not be assigned to DNS server which is on a directly connected network on Thu, 18 Feb 2021 15:35:38 GMT]]></title><description><![CDATA[<p dir="auto">OK I'm dumb... <img src="https://forum.netgate.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f926.png?v=d00e50224fa" class="not-responsive emoji emoji-android emoji--face_palm" style="height:23px;width:auto;vertical-align:middle" title=":face_palm:" alt="🤦" /> <img src="https://forum.netgate.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f926.png?v=d00e50224fa" class="not-responsive emoji emoji-android emoji--face_palm" style="height:23px;width:auto;vertical-align:middle" title=":face_palm:" alt="🤦" /></p>
<p dir="auto">It's obvious that this gateway will be used to reach 192.168.255.254 DNS since it is a direct attached subnet... There is no risk that it uses any other gateway...</p>
<p dir="auto">I sticked too hard to the rule "at least one DNS must be set per gateway in a multiwan environment" In the case of a DNS in a WAN subnet, selecting none is fine because routing through this interface is implicit.</p>
<p dir="auto">My use case is not the most widespread but maybe a clarification could be made in the <a href="https://docs.netgate.com/pfsense/en/latest/multiwan/interfaces-and-dns.html#multiwan-dns-servers-and-static-routes" target="_blank" rel="noopener noreferrer nofollow ugc">documentation</a>. Meanwhile answer can now be found here <img src="https://forum.netgate.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f60a.png?v=d00e50224fa" class="not-responsive emoji emoji-android emoji--blush" style="height:23px;width:auto;vertical-align:middle" title=":blush:" alt="😊" /></p>
]]></description><link>https://forum.netgate.com/post/964762</link><guid isPermaLink="true">https://forum.netgate.com/post/964762</guid><dc:creator><![CDATA[geminux]]></dc:creator><pubDate>Thu, 18 Feb 2021 15:35:38 GMT</pubDate></item></channel></rss>