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

    Local Web Server Access from within…

    Scheduled Pinned Locked Moved DHCP and DNS
    16 Posts 4 Posters 7.8k 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.
    • GruensFroeschliG
      GruensFroeschli
      last edited by

      Before i can post screenshots i need to know more about how your setup is (there is more than one way to accomplish what you want)

      Could you tell us if you are forwarding single ports to the servers?
      Or are you 1:1 NATing?
      Did you create VIP's on the WAN for your servers?

      We do what we must, because we can.

      Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

      1 Reply Last reply Reply Quote 0
      • M
        mikeyh
        last edited by

        Thank you very much for taking the time.

        I have set external IP in the 1:1 to the internal IP of each server.

        I tested thru anonymous proxy servers that everyone can get to the web sites.

        I setup the VIP's on the WAN and also set the port forwarding of the ports that needed to be went to the servers. I also created the allow rules. I can get to the servers via their internal IP addresses.

        Other than not being able to just type the web name in, one of the main problems are, I can't send email to a couple of the other mail servers via: "someone@echovalve.com" or "someone@bmhnc.com" for example.

        Thanks again,

        1 Reply Last reply Reply Quote 0
        • GruensFroeschliG
          GruensFroeschli
          last edited by

          In the link Perry posted above i wrote:

          NAT-Reflection does not work with 1:1 NAT
          http://forum.pfsense.org/index.php?topic=7266.msg41244
          quote:
          You most likely need to setup split dns or add a port forward on top of the 1:1 nat to invoke reflection.  Reflection by default does not work with 1:1 nat's.    So your most likely resolving the public IP address which will not forward back across to the 1:1 server.

          I attached below how this looks like for a server in my DMZ.
          I might be not obvious but you can leave the host-field blank and thus foward a domain.
          I have to do this because at my home i have double NAT and the resolved name is no the IP i have on WAN.

          DNS_forwarder_override.JPG
          DNS_forwarder_override.JPG_thumb

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

          1 Reply Last reply Reply Quote 0
          • M
            mikeyh
            last edited by

            Thanks again for the screen shot. I had the settings like that already. I've been reading all of the information I could find before asking for help. I flushed the configuation out again and re-set it back up and it still doesn't work.

            I have the 1:1 set as: 69.38.85.173/32 –> 192.168.0.1/32 then:

            Port Forward I have:

            If                Proto            Ext. port range                NAT IP              Int. port range                      Description

            WAN          TCP/UDP            80 (HTTP)                  192.168.0.1                                                    Web 1
                                                                                (ext.: 69.38.85.173)        80 (HTTP)

            Rules WAN

            Proto      Source        Port            Destination            Port            Gateway          Schedule            Description

            TCP/UDP      *              *              192.168.0.1          80 (HTTP)          *

            1 Reply Last reply Reply Quote 0
            • GruensFroeschliG
              GruensFroeschli
              last edited by

              Is 192.168.0.1 the IP of your server?
              The NAT IP has to be the IP of your server.

              We do what we must, because we can.

              Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

              1 Reply Last reply Reply Quote 0
              • M
                mikeyh
                last edited by

                Internal IP of the server is:  192.168.0.1
                External IP of the server is:  (ext: 69.38.85.173)

                The external IP shows up in brackets in the same box but, below the internal IP

                1 Reply Last reply Reply Quote 0
                • P
                  Perry
                  last edited by

                  Some lan nic info could be nice maybe a diagram too…..

                  /Perry
                  doc.pfsense.org

                  1 Reply Last reply Reply Quote 0
                  • GruensFroeschliG
                    GruensFroeschli
                    last edited by

                    Just to be sure: your clients have as DNS the pfSense right?

                    We do what we must, because we can.

                    Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

                    1 Reply Last reply Reply Quote 0
                    • M
                      mikeyh
                      last edited by

                      Our main server has always been the DNS server for all of our internal computers. It is configured in the DHCP services on that server. It has 2 entries that point to my ISP's DNS servers.
                      Should I remove these entries and just put the one for the pfSense in their place?

                      One of the NIC cards (LAN side) is on the mother board. The computer is a Dell Optiplex GX110. The other is a US Robotics 10/100/1000.

                      Again, thank you guys very much for ALL of your help!!!

                      1 Reply Last reply Reply Quote 0
                      • H
                        hoba
                        last edited by

                        You can manually add the dns-entry to your local dns server as well to resolve it to the internal IP instead of forwarding the request to the external dns servers which resolves the public IP. Check the manpages of your dns server how to do that.

                        1 Reply Last reply Reply Quote 0
                        • M
                          mikeyh
                          last edited by

                          I added the internal IP address of the pfSense to the DNS Server list in my SBS 2003 and still the same result…

                          1 Reply Last reply Reply Quote 0
                          • H
                            hoba
                            last edited by

                            That's not the same like entering the pfSense dnsforwarder as forward dns lookup. If it's just an additional DNS and not the frst one it will ask the first DNS server and as that resolves to the public IP it won't ever ask the pfSense dns forwarder.

                            1 Reply Last reply Reply Quote 0
                            • M
                              mikeyh
                              last edited by

                              Update on DNS issues. After removing my real DNS server entries from my SBS 2003 and adding the pfSense as the only entry, and following the previous instructions of adding the internal Web Servers local names and addresses in the DNS Forwarder area of the pfSense, all is well.

                              Thanks again very much.

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