Correct. The only ports it cares about as far as A records are concerned are 80/443, meaning that I can’t make an A record for my FQDN that points to xxx.xx.80.9:9000. My guess is I’m going to have to setup a proxy in order to serve the page to my FQDN instead of xxx.xx.80.9:9000. Either that or change the default port to 443 but I think I would have to give Graylog root privs to do that and I don’t wanna do that.
Hey @lawdfarquhar
I really dont think you need to go that route, DNS uses port 53 but does listing to all ports unless specified.
For example if i create a graylog server and called it lawdfarquhar.com IP 192.168.1.100. I then create a A record and you good for that domain and depending on the DNS server setting on how far can reach. meaning is it a lab or production. Also if you have graylog on Linux node, what I do is set the /etc/hosts file like so…
[root@graylog mongodb]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.100 lawdfarquhar.com
[root@graylog mongodb]#
With the /etc/hostname file, I ensure its the same as the /etc/hosts file and the certitificates I create.
EDIT: @lawdfarquhar
If you do go with a reverse proxy might want to check out this post.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.