You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some scenarios where split DNS is used internally, you want to be able to check both destinations. The only way to do this is to specify the target IP instead of the FQDN. Having multiple IPs then, it is hard to determine what device it is without doing internal IP search.
Therefore, having the ability to add a "friendly name" or "description" to a target would solve this within the file.
Example:
domain.com 443 # load balancer 1
anotherdomain.com 443 # web server xyz
The text was updated successfully, but these errors were encountered:
In some scenarios where split DNS is used internally, you want to be able to check both destinations. The only way to do this is to specify the target IP instead of the FQDN. Having multiple IPs then, it is hard to determine what device it is without doing internal IP search.
Therefore, having the ability to add a "friendly name" or "description" to a target would solve this within the file.
Example:
domain.com 443 # load balancer 1
anotherdomain.com 443 # web server xyz
The text was updated successfully, but these errors were encountered: