<?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[Whitelist wildcard domains &#x2F; hosts]]></title><description><![CDATA[<p dir="auto">Hello</p>
<p dir="auto">Can anybody suggest a way to implement whitelisting of domains using a wildcard on the pfSense CP?</p>
<p dir="auto">The only discussions I can find on this subject is this thread from a few years ago:</p>
<p dir="auto">https://forum.pfsense.org/index.php?topic=44264.0</p>
<p dir="auto">That thread mentions that this was done in a private build and was performing well, however I cannot find any further information on it.</p>
<p dir="auto">My end objective here is to use an external hosted portal that allows people to login using Facebook/Twitter etc. and that requires me to whitelist a couple of CDNs and some other domains using a wildcard i.e. *.cloudfront.net, *.akamaihd.net  etc.</p>
<p dir="auto">I wouldn't be against proposing a bounty to make this feature available if someone could explain a sensible way of doing this that would scale reasonably well and would be prepared to put the work into adding the support to the GUI (though frankly even if a reasonable spec box was only able to handle 1-2k clients I can just deploy multiple ones and distribute clients across them).</p>
]]></description><link>https://forum.netgate.com/topic/70461/whitelist-wildcard-domains-hosts</link><generator>RSS for Node</generator><lastBuildDate>Mon, 08 Jun 2026 14:16:00 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/70461.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 20 Jun 2014 11:08:03 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Whitelist wildcard domains &#x2F; hosts on Sat, 21 Jun 2014 15:40:42 GMT]]></title><description><![CDATA[<p dir="auto">As jimp already explained (implicit), you should intercept all DNS requests, and match them with the with listed domain names.<br />
If you have a match, the resulting IP should be fed into the allowed IP list of the portal page. You probably have to issue en redirect to your client.<br />
Some caching will needed, otherwise portal access will slow down as easy DNS request has to be filtered.</p>
<p dir="auto">This is what I should call a "bounty project".</p>
]]></description><link>https://forum.netgate.com/post/468524</link><guid isPermaLink="true">https://forum.netgate.com/post/468524</guid><dc:creator><![CDATA[Gertjan]]></dc:creator><pubDate>Sat, 21 Jun 2014 15:40:42 GMT</pubDate></item></channel></rss>