How to tell k1000.domain.com to search for hostname.domain.local?
Some time ago, we migrated our K1000 from domain.local to domain.com in order to allow external connectivity. Since that time, we've run into intermittent issues where the K1000 is not able to find internal hosts. Running nslookup hostname 10.0.0.1 (as an example) will find the IP address of the host using the DNS server at 10.0.0.1 where the nslookup utility of the K1000 (which will show that it is running against the exact same DNS server; 10.0.0.1) will occasionally not be able to find it. Running nslookup from the K1000 to hostname.domain.local does work, however.
The issue is very intermittent, to the point where it works about 90% of the time. When it doesn't work, it usually resolves after doing an nslookup to hostname.domain.local; after that point, nslookup to hostname will work. Occasionally (like now), I am unable to resolve the hostname at all, regardless of what I do.
Furthermore, even running the runkbot 4 0 command from the host does not cause it to appear in inventory or provide a successful nslookup from the K1000 to the hostname.
Answer Chosen by the Author
For the benefit of anyone who finds this article while researching this exact same issue, we believe we found the resolution:
Under Settings/Control Panel/Network Settings, the "Web Server Name" is listed as hostname.domain.com. "Autogenerate Server Name" is de-selected, and "Domain" is listed as domain.local.
Answered 08/15/2016 by: firstname.lastname@example.org
Please log in to comment
log in to commentPlease