You know, that's an excellent idea.
I will compile a short list of hosts to test with and let you know the outcome.
Sincerely,
Jesse
-----Original Message----- From: nav-users-request@uninett.no [mailto:nav-users-request@uninett.no] On Behalf Of Jan Sigurd Refvik Sent: Friday, August 8, 2014 12:14 AM To: 'jorr@streamguys.com'; nav-users@uninett.no Subject: RE: Sysname () is already in database
Hello,
I am demoing out the NAV appliance and we have a number of physical and virtual hosts that do not have reverse DNS entries available, resolution of the IPs belonging to the hosts results in
unknown.domainname.tld.
When attempting to add multiple hosts to the NAV seed database, I receive errors when NAV attempts to resolve the DNS name of the host, claiming that the host already exists, despite all unique information with the exception of the failed resolution of the fqdn.
Is there a work-around so that NAV does not lookup the DNS name of said devices?
Maybe a list in /etc/hosts could work?