The disclosure herein describes managing multiple clusters within a container environment using a control cluster. The control cluster includes a single deployment model that manages deployment of cluster components to a plurality of clusters at the cluster level. Changes or updates made to one cluster are automatically propagated to other clusters in the same environment, reducing system update time across clusters. The control cluster aggregates and/or stores monitoring data for the plurality of clusters creating a centralized data store for metrics data, log data and other systems data. The monitoring data and/or alerts are displayed on a unified dashboard via a user interface. The unified dashboard creates a single representation of clusters and monitor data in a single location providing system health data and unified alerts notifying a user as to issues detected across multiple clusters.

A method and a computer system for performing the method of determining an initial value or lifetime value for a domain name is provided. The method for determining an initial value includes obtaining, over a communication network, a domain name from requestor; obtaining, over the communication network, one or more inputs from one or more domain name data sources; applying the one or more inputs and the domain name to an initial lifetime worth computer model, wherein the one or more inputs comprise data related to comparable historical domain names, data from a linguistic model analysis, data from a linguistic frequency list, and data related to a second-level domain to top-level domain relationship analysis; determining, by a hardware processor, an initial lifetime worth for the domain name based on the initial lifetime worth computer model; and providing the initial lifetime worth for the domain name to the requestor.

A method for providing topology information, use of a name service server, a device, a computer program, a computer-readable medium and a method for configuring a device to be named within an industrial network, wherein a) the device to be named receives a neighbouring name message from a neighbouring device, b) a self-naming module creates a topological neighbouring domain name based on the neighbouring name message, c) the self-naming module transmits the topological neighbouring domain name to a name service server, d) the self-naming module receives from the name service server a response message, which includes at least one device name of the device to be named belonging to the topological neighbouring domain name, and e) at least one device name from the response message is assigned to the device to be named and this name is stored as the device name by the self-naming module.

Methods for operating a device and for managing bootstrapping of devices are disclosed. The method (100) for operating a device comprises computing (102) a derivative of a secret shared between the device and a server entity of a network, generating (104) a temporary bootstrap URI by combining at least a part of the computed derivative with a static bootstrap URI for the network, and sending (106) a bootstrap request to the temporary bootstrap URI. The method for managing bootstrapping of devices comprises generating temporary bootstrap URIs corresponding to devices operable to connect to a network, and updating a network DNS registry to map the generated temporary bootstrap URIs to the IP address of at least one of a bootstrap server instance reachable via the network and/or a bootstrap load balancer. Also disclosed are a device, a bootstrap load balancer, a bootstrap server, and a computer program.

A communication apparatus that transmits data outside via different communication interfaces performs operations, including setting an interface correspondence between a domain name identifying a domain and a communication interface for use with an external apparatus belonging to the domain, generating, from the set interface correspondence, a setting indicating a Domain Name System (DNS) server correspondence between the domain name and the DNS server to which name resolution for a host name of the external apparatus is to be transferred, and activating a DNS cache server that operates from the generated setting. A DNS client requested for the host name resolution by an application of the communication apparatus transmits a name resolution request to the DNS cache server. Based on the received host name, the DNS cache server determines an external DNS server to which the name resolution is requested, and requests the determined external DNS server for the name resolution.

Systems, apparatuses, and method are described for resolving domain names based on localization. A computing device may send, to a name server, a request indicating a domain. The name server may determine one or more servers associated with the domain based on the locations of the one or more servers and/or the computing device. The name server may send, to the computing device, a message indicating the determined one or more servers.

A system and method are provided for a network device for use with a client device having a hostname and a MAC address. The network device contains a memory that has a second hostname and a second MAC address stored within the memory. The second MAC address corresponds to the second hostname. The memory also contains a processor configured to execute instructions stored on the memory to cause the network device to: receive, from the client device, the hostname and the MAC address; determine whether the MAC address is randomized; provide an instruction to the client device to inform a user of the client device that the client device hostname is registered when the hostname matches the second hostname and the MAC address is randomized.

Guest-to-host virtual networking can include linking a virtual entity proxy to a network adapter of a host machine through a virtual bridge. In response to a request that starts a guest running on the host machine, the guest can be configured to point to the virtual entity proxy and to communicatively couple to a network through the virtual entity proxy linked to the network adapter of the host machine. The virtual entity proxy can be bound to the network, such that the virtual entity proxy intermediates communications between the guest and one or more other guests running on one or more different host machines that are also communicatively coupled to the network.

Example methods are provided for assigning a routing domain identifier in a logical network environment that includes one or more logical distributed routers and one or more logical switches. In one example, the method may comprise obtaining network topology information specifying how the one or more logical distributed routers are connected with the one or more logical switches; and selecting, from the one or more logical switches, a particular logical switch for which routing domain identifier assignment is required. The method may also comprise: identifying a particular logical distributed router that is connected with the particular logical switch based on the network topology information; assigning the particular logical switch with the routing domain identifier that is associated with the particular logical distributed router; and using the routing domain identifier in a communication between a management entity and a host.

A method for managing and routing client queries within an entity is provided. The method may include receiving a client query including origination identification data associated with a sender of the client query. In response to searching in a database for history correlating to the origination identification data, determining that no relevant history exists with respect to the origination identification data. The method may include identifying the sender by identifying, within the query, a first character string identical to a first keyword stored in a classification model within a database, using the first keyword to identify a second character string that includes the first keyword in addition to other characters, identifying, from a list of sub-entities, a sub-entity associated with the first keyword and using a combination of the first keyword, the sub-entity and one or more attributes to identify the sender as an existing client.