Blocking Users From Accessing NagiosXI via IP Address

[luczynj]

Hello Support Team,

We would like the ability of preventing users from logging onto Nagios XI via the IP address URL. But it should allow administrators from using the IP addresses.

We have a primary and backup instance of Nagios XI running in production. We also have a DNS address pointing to whichever instance is the current primary. However, we're seeing users logging onto the logical backup server. (This is why my previous post asks for the ability to be able to select all users (except admins) and disable them.).

Any assistance would be appreciated. We have toyed with the idea of having a backup DNS name pointing to the logical backup, but wanted to run it past you first.

Regards,
JL

[jbrunkow]

I think a feature like that would be a function of your local DNS or firewall. Nagios XI does not currently offer provisioning access over one method or the other. You could also put the test server on another network that only your administrators could access. It just depends on what networking resources you have available.

[luczynj]

Along the same area, is there anything within the configuration of the Nagios XI installtion/settings where the server is referred to as an IP address versus a DNS domain name?

But if we have IP address 100.100.100.1 as the IP address of our primary Nagios XI server and 100.100.100.2 as the backup Nagios XI server, then when we switch the DNS name to point from .1 to .2, is there any potential issues this could cause?

I think we had an issue with reports that were failing and you (Nagios Support) found the end result was how the server was defined. I think the report was pointing to an IP address URL? I'll have to check my emails.

Thanks,
JL

[jbrunkow]

The addresses that certain URLs resolve to is a function of your DNS, not of Nagios. Nagios does not have a built-in feature that allows domain configuration.

If you want to find out which name server is responsible for the domain in question, you could run a command like the one below on a Linux machine.

Code: Select all

host -t ns <address>

You could also perform a whois lookup by running a command of the same name. This would return more helpful information about who is responsible for that domain.

Code: Select all

whois <address>

Yes, there are issues that could arise from changing the IP address at the end of that DNS record. Certain people could have the link saved as an IP address, or cached to their browser. You may have to update whatever files or materials contain the old address, or even send out a communication notifying your department of the change.

Let me know if you find the emails. I would be happy to help inform on whatever steps you think may be helpful.