DNS needed for local access to webserver behind pfSense
eiger3970 last edited by
The computer has DNS settings 22.214.171.124 and 126.96.36.199.
I tried a port forward on pfSense to 127.0.0.1:53, but this messed up the loading of the websites.
www.domain1.com loads in the LAN, but not outside the public WAN. (actually, only the index.html opens).
www.domain2.com doesn't load anymore, which I'm trying to fix.
ember1205 last edited by
What if you were to load DNS zones directly on the web server and set security on them to hand out the private addresses of the servers to local clients. The "rest" of the Internet would use forwarding through the pfSense system (or use the pfSense system as an upstream resolver). Point the clients to the DNS on the web servers.
what dns server - you host your own name servers? What domain? PM it if you don't want a public website to be known public for some reason ;)
So you created port forwards for your website and dns to get to your name server? Public facing dns should always have 2 name servers at min.. Any decent registrar would require that anyway. So where is your secondary name server?
it is really hard to troubleshoot dns related problems of this nature without actually knowing and being able to query the nameserver to tell you what its doing wrong or right, etc. Off the cuff, pretty much anyone hosting their own dns to the public is most likely doing it wrong ;) let a company host your dns that does that for their bread and butter, etc… Hosting dns on global infrastructure can be had for less than it costs to power the box hosting your dns ;) Why would you not enjoy a global dns setup with anycast, failover, etc. etc.. for $30 a year for 5 million queries a month, etc. etc..
It almost never makes sense to host your own dns that is public facing.. But sure lets get you working ;)