Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    DNS needed for local access to webserver behind pfSense

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 3 Posters 808 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      eiger3970
      last edited by

      I run a webserver with DNS server and websites are accessible from outside the public WAN.
      However on a computer in the LAN, www.domain1.com and www.domain2.com load the pfSense Login page.

      The computer has DNS settings 8.8.8.8 and 8.8.4.4.

      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.

      1 Reply Last reply Reply Quote 0
      • E
        ember1205
        last edited by

        Split DNS?

        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.

        1 Reply Last reply Reply Quote 0
        • johnpozJ
          johnpoz LAYER 8 Global Moderator
          last edited by

          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 ;)

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.11 | Lab VMs 2.8, 24.11

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.