Issue with FQDN
-
@christophergault said:
Hey, so I got HipChat server installed on my TD350 but I need to access it through hipchat.gaultnetwork.com. How do I do this?
A lot more information is needed.
But at the highest level,of in to your DNS provider for gualtnetwork.com and add an A record pointing to the public IP that your server is sitting behind.
Assuming that your port forwarding and firewalls are all setup right, it will work.
-
@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...
-
you don't add ports to the DNS server, that is handled by the firewall you have in front of the hipchat server you're hosting, unless your hipchat server is directly on the internet.
-
@Dashrender I have a Cisco Meraki MX64...
-
@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.
-
@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?
-
@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...
-
unless you use something like nginx you can't put two services on the same port on the same IP address.
-
@Dashrender Well there different servers...
-
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.
-
@Dashrender publish?
-
@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 -
@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.
