<?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] Windows IIS Webserver with Pfsense = Potential Rebind Attack]]></title><description><![CDATA[<p dir="auto">Sorry if I post this in the wrong section.</p>
<p dir="auto">I have a Pfsense 2.3.3-RELESE-P1<br />
Virtual IP Adress setup with IP Alias<br />
NAT 1:1 mapping<br />
Dns Forwarder enabled<br />
A test webb server with two subdomains test1.example.org and test2.example.org</p>
<p dir="auto">Which results in Potential Rebind Attack if I try to access any of the sites</p>
<p dir="auto">I have tried both suggestions in this faq; <a href="https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks" target="_blank" rel="noopener noreferrer nofollow ugc">https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks</a></p>
<p dir="auto">If I enabled NAT reflektion, the sites become inaccessible</p>
<p dir="auto">If I map split dns - the end result is the same - Potential Rebind Attack</p>
<p dir="auto">What am I doing wrong?<br />
Thanks in advance!<br />
Regards</p>
<p dir="auto">EDITED;</p>
<p dir="auto">I have another network on the Pfsense box which I used to test the webserver and my firewall rules is most likly the problem since it seems to resolv internal rather then go externaly. I have replaced this network with another router and now it works.<br />
So stupid of me but "learning by doing".</p>
<p dir="auto">Regards</p>
]]></description><link>https://forum.netgate.com/topic/115685/solved-windows-iis-webserver-with-pfsense-potential-rebind-attack</link><generator>RSS for Node</generator><lastBuildDate>Wed, 15 Jul 2026 05:10:35 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/115685.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 15 May 2017 08:27:55 GMT</pubDate><ttl>60</ttl></channel></rss>