Service Management

Service Management is the place to connect DNS/DHCP and IPAM services that you want to orchestrate with Micetro. These services can be hosted on-premises, on appliances, or in the cloud. Services that have been connected are listed on the Service Management on the Admin page.

  1. Select Admin on the top navigation bar.

  2. Click Service Management on the menu bar at the top of the admin workspace.

    • By default, all services configured in the system are shown.

    • In the left pane you can filter the list by type of service or provider.

    • In the right pane, the properties of a selected service are shown.


The Micetro web interface does not yet provide full management of IPAM services. Therefore they are not listed here, but you can still enable IPAM services by using the Add service function.

Depending on the user permissions and available license keys, DNS and DHCP services and functions can be disabled or hidden.

Micetro has a granular role based Access Management system. For DNS and DHCP administrators, it is recommended to be members of the built-in DNS Administrators and/or IPAM Administrators roles. To manage Appliances, it is recommended to be a member of the built-in Administrators role.

When not using the built-in roles, users need to be members of a role with the following permissions. Note that other permissions could be needed to manage the services fully. For more information on Micetro’s granular role-based access controls, see Access Management.

  • To manage DNS services: Administer DNS servers

  • To manage DHCP services: Administer DHCP servers

  • To manage cloud services: Access to manage clouds

  • To manage appliance services: Administer appliances

Supported Platforms

Micetro supports the following DNS and DHCP platforms

  • DNS

    • AuthServe

    • AWS Route 53 (cloud)

    • Azure DNS (cloud)

    • BIND

    • DynDNS (cloud), (Note DynDNS is EOL May 31st 2023)

    • Edge DNS (cloud)

    • Microsoft DNS

    • NS1 (cloud)

    • Unbound (deprecated, new services cannot be added)

    • Men&Mice Appliance

    • Men&Mice caching Appliance

  • DHCP

    • Cisco IOS

    • ISC DHCP

    • Kea

    • Microsoft DHCP

    • Men&Mice Appliance

Micetro Agents

To handle communication between Micetro and the external service, an Agent is needed. Depending on the type of service and if it’s on-premises or cloud, the agent is either installed on the respective machine, on the machine running Men&Mice central or, in some cases, on any machine that is in the same domain as the DNS/DHCP servers. A single agent can handle communication with multiple servers. For more information on agents and how to install them, see Micetro Agents.


When managing Microsoft DNS servers on remote computers with the DNS Server Controller, some actions for static zones may not be available:

  • Disable resource record

  • Enable resource record

  • View and edit record comments

  • Disable zone

To perform these actions, you need to install the DNS Agent on the server and use that connection when adding the server.

Adding a Service

You must have the permission to administer DNS to add a new service to Micetro.

Adding a new service is either a two or three step process, depending on the type of service being added.

  1. Select Admin on the top navigation bar.

  2. Click Service Managment on the menu bar at the top of the admin workspace.

  3. Click Add Service. The Add Service wizard opens.

  4. Choose the platform you want to use. You’ll see a list of options to choose from, based on your license keys, DNS and IPAM. You can use the DNS, DHCP, and IPAM filters at the top to narrow down the list. You can also use the search box to search for the right service.

  5. Select an agent:

    • This step is skipped for cloud services.

    • For ISC BIND and ISC DHCP this step is skipped, as the agent must be installed on the service host.

    • With the exception of the service types mentioned above, the agent can be installed on the Micetro Central host, on the Service host, or in the case of MS DNS/DHCP, ISC Kea, and Cisco IOS on a different host. If you have already added a service of this type before, you have the opportunity to either select from existing agents or create a new agent. A single agent can be used to manage multiple connections.


    • In the case of AuthServe, you can select from a list of available agents that were registered in the installation process.

    • For AuthServe git you can also register a new agent on the New Agent tab. Enter a hostname for the agent and, optionally, the IP address. If the hostname is not resolvable, an IP address is needed here.

  6. Add service:

  • Cloud services: Each service type has its set of credentials in addition to the optional service name.

  • On-premises services

    • Provide the hostname or IP address of the service/server.

    • AuthServe uses channel as the connection string. Channel name is mapped to a host name in a configuration file on the server. ‘ansp’ is the default channel name which maps to localhost. To select a different host name the syntax is "<someseceret>". Refer to AuthServe documentation for details.

Editing Services

Depending on the service, you can change the name and/or custom properties for the service. For example, if you need to refer to the service by another name or if you are connecting to the service by an IP Address and the IP Address has changed.

To edit a service:

  1. Locate the service you want to edit in the Service Management area.

  2. Double click the service or select it, and then select Edit service on the Action menu.

  3. Make the necessary changes. Click Confirm to save the changes.

Other Service Actions

Depending on the selected service you can edit name and/or custom properties for the service. Any actions that can be performed on a selected server can either be accessed in the Actions above the list or by clicking the Row menu (…) button that appears when you hover over the right hand side of a row.



Attach service

Attaches a previously detached server/service.

Detach server

Detaches or disables the server/service. When a server is detached, it is not synchronized with Micetro and excluded from various checks. When a server is detached, it is greyed out in the service view grid. The server can be attached again for it to be part of the server synchronization again.

View history

Allows to view history for the selected server/service.

Remove service

Removes the selected server/service from Micetro. This option is only available with the Administrator account.


Triggers synchronization of zones and records or scopes.

Service States

The list of services shows an indicator of the state of the individual services configured in the system.

The indicators can refer to either the Server Controller (see Micetro Agents) running on the DNS/DHCP server, or the DNS/DHCP server service itself.

Use the following table for more information on the indicators:






The status of the DNS/DHCP Server Controller is unknown.


Server, Controller

The DNS/DHCP Server Controller and service are both OK.



The DNS/DHCP Server Controller is offline or otherwise unreachable.

Out of date


The DNS/DHCP Server Controller has a different version than Central.



The DNS/DHCP Server Controller is being updated.



The DNS/DHCP server is uninitialized and needs to be manually initialized.



The DNS/DHCP server has been detached without removing it from Micetro.

Service Down


The DNS/DHCP server is down and not responding to queries.

Service Impaired


The DNS/DHCP server is running but impaired. [1]

DHCP Services

For detailed information about the different DHCP platforms and their configurations, refer to: