Is there a way to get the discovery image to generate and register the FQDN
of a discovered host? I would like it to be autogenerated, say
'mac005056b59e3f.discovered.example.com' and register both A and PTR
records. Thanks.
Not at the moment, no. Currently we don't assume which subnet the host
should belong to, nor which domain - these things are very hard to infer
from the data we have a-priori (we only know the IP, which might not be
enough to identify a subnet, and the proxy used to reboot the host, which
might have many subnets and domains).
We could add options in the Settings page to associate a discovered host to
a subnet / domain, but that would conflict if you have discovery happening
on multiple subnets.
Overall, since these names are intended to be temporary ones until the host
is properly provisioned, we felt it easier to just not assign a
domain/subnet at all.
Greg
···
On 20 October 2014 15:01, lawre wrote:Is there a way to get the discovery image to generate and register the
FQDN of a discovered host? I would like it to be autogenerated, say ‘
mac005056b59e3f.discovered.example.com’ and register both A and PTR
records. Thanks.
There are plans to create simple scoped_search-based set of rules that
will allow you to assign host groups with hostname to be configurable.
Stay tuned.
···
On Mon, Oct 20, 2014 at 03:08:53PM +0100, Greg Sutcliffe wrote: > On 20 October 2014 15:01, lawre wrote: > > > Is there a way to get the discovery image to generate and register the > > FQDN of a discovered host? I would like it to be autogenerated, say ' > > mac005056b59e3f.discovered.example.com' and register both A and PTR > > records. Thanks. > > > > > Not at the moment, no. Currently we don't assume which subnet the host > should belong to, nor which domain - these things are very hard to infer > from the data we have a-priori (we only know the IP, which might not be > enough to identify a subnet, and the proxy used to reboot the host, which > might have many subnets and domains).–
Later,
Lukas #lzap Zapletal