ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Issue with FQDN

    IT Discussion
    4
    14
    2.4k
    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.
    • C
      christophergault @Dashrender
      last edited by

      @Dashrender I have a Cisco Meraki MX64...

      scottalanmillerS 1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @christophergault
        last edited by

        @christophergault said:

        @JaredBusch I have tried portforwarding and it works on the Meraki side but cloudflare DNS dosn't like ports added to the public IP address...

        This has nothing to do with CloudFlare. DNS is an IP to Hostname mapping service. There is no concept of layer 4 (ports) in DNS. You cannot use DNS to do port mapping.

        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @christophergault
          last edited by

          @christophergault said:

          @Dashrender I have a Cisco Meraki MX64...

          So the base question is...

          What port is HipChat running on (on the server.) And what port do you want to expose through the Meraki to the outside world?

          C 1 Reply Last reply Reply Quote 0
          • C
            christophergault @scottalanmiller
            last edited by

            @scottalanmiller Im also trying to get gitlab to work and its on port 81... I just want to type it gitlab.gaultnetwork.com and get to the server...

            scottalanmillerS 1 Reply Last reply Reply Quote 0
            • DashrenderD
              Dashrender
              last edited by

              unless you use something like nginx you can't put two services on the same port on the same IP address.

              C 1 Reply Last reply Reply Quote 0
              • C
                christophergault @Dashrender
                last edited by

                @Dashrender Well there different servers...

                1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender
                  last edited by

                  That's not atypical. But you'll need a third one running nginx. nginx is what you will publish through the Meraki firewall, then behind the ngix box you'll have your two servers.

                  C 1 Reply Last reply Reply Quote 0
                  • C
                    christophergault @Dashrender
                    last edited by

                    @Dashrender publish?

                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch @christophergault
                      last edited by

                      @christophergault said:

                      @Dashrender publish?

                      That is the wrong word.

                      What he is trying to tell you is that you need to use a reverse proxy in your setup. You will port forward port 80 and 443 (if using SSL) to the internal IP of the proxy.

                      The proxy will then connect to the internal ip of the server in question based on the DNS name you have setup.

                      You will never use non standard ports in a normal setup. Each of your individual servers behind the proxy will be on port 80/443/whatever.

                      Nginx is a fairly standard webserver with solid proxy capabilities.

                      I have a write up here on how to set it up.
                      http://mangolassi.it/topic/6905/setting-up-nginx-on-centos-7-as-a-reverse-proxy

                      1 Reply Last reply Reply Quote 1
                      • scottalanmillerS
                        scottalanmiller @christophergault
                        last edited by

                        @christophergault said:

                        @scottalanmiller Im also trying to get gitlab to work and its on port 81... I just want to type it gitlab.gaultnetwork.com and get to the server...

                        Then you need it to be on port 80. Non-standard ports cannot be specified without putting them into the browser. it would be like sending someone to an apartment complex but not telling them the apartment number.

                        1 Reply Last reply Reply Quote 1
                        • 1 / 1
                        • First post
                          Last post