<?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[Accessing a site - DNS flush]]></title><description><![CDATA[<p dir="auto">Hello. We have a site that our users cannot connect to. When they try, they get a message "Site can't be reached. dns_probe_finished_nxdomain".</p>
<p dir="auto">The URL sites:</p>
<ul>
<li>https://link.nyulangone.org/EpicCareLink/common/epic_login.asp</li>
<li>https://link.nyulangone.org/</li>
</ul>
<p dir="auto">We have cleared (flushed) the DNS cache in PFSense.</p>
<ul>
<li>Status &gt; Services &gt; unbound</li>
</ul>
<p dir="auto">We have restarted and also stopped and started DNS Resolver.</p>
<p dir="auto">Afterwards, the site will randomly work or not; sometimes, by itself, the portal will come up. We have tried in private windows of all browsers.</p>
<p dir="auto">If a user is able to log in, it is only for a few minutes, and the user is kicked off.</p>
<p dir="auto">Any troubleshoots or fixes we can try?</p>
]]></description><link>https://forum.netgate.com/topic/177464/accessing-a-site-dns-flush</link><generator>RSS for Node</generator><lastBuildDate>Sun, 14 Jun 2026 03:57:05 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/177464.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 31 Jan 2023 20:53:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Accessing a site - DNS flush on Tue, 31 Jan 2023 21:13:49 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jlee_eye">@<bdi>jlee_eye</bdi></a> link.nyulangone.org has a 30 second TTL so any DNS problems can break/resolve every few seconds.</p>
<p dir="auto">If you try nslookup does that work during an "outage"?</p>
<p dir="auto">nslookup link.nyulangone.org your_pfsense_ip</p>
<p dir="auto">Are your PCs using pfSense for DNS?</p>
<p dir="auto">It's also very possible your browser is using DNS over HTTPS and not using pfSense for DNS at all.  Many default to that nowadays.</p>
]]></description><link>https://forum.netgate.com/post/1083405</link><guid isPermaLink="true">https://forum.netgate.com/post/1083405</guid><dc:creator><![CDATA[SteveITS]]></dc:creator><pubDate>Tue, 31 Jan 2023 21:13:49 GMT</pubDate></item></channel></rss>