mnagel

option to require FQDN

Recommended Posts

As we have run into numerous cases now where the device name uniqueness requirement has bitten us, my recommendation to LM is now this:

   * add a portal option to require a FQDN for all devices -- failure to include would cause rejection
   * add an option to have a default FQDN suffix defined as a group property which would be used when adding a new device within that group

I am not sure what to suggest for Websites and the new Services naming, but similar issues apply, especially for the current RBAC-based MSP model.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.