TECHZEN Zenoss User Community ARCHIVE  

DNS resolution fails during Discovery

Subject: DNS resolution fails during Discovery
Author: [Not Specified]
Posted: 2015-04-26 23:26

After installing zenoss and getting logged in for the first time I ran discovery on four of my largest IP ranges. it would appear the discovery worked, however name resolution did not. all devices were added by their IP address instead of their dns name as expected.

tested the command as i understand it for both forward and reverse by running the commands as defined in an ssh window. the commands worked fine. when the same commands are run via the zenoss UI I get a timeout. this is probably something simple, possibly rights related. has anyone else has this problem



Subject: Still can't seem to find a
Author: [Not Specified]
Posted: 2015-04-28 12:08

Still can't seem to find a resolution for this. can anyone tell me how these commands are run via the zenoss interface vs. a putty session over ssh trying to understand why this would time out through Zenoss, despite the server being able to resolve them.



Subject: Today i tried to install
Author: [Not Specified]
Posted: 2015-05-01 13:53

Today i tried to install percona, and some zenpacks. i realize now that this resolution issue may have something to do with how zenoss runs commands, and my fundamental misunderstanding of how docker and control center are running commands. is there documentation somewhere on how this all works. as it stand i'm unable to download any zenpacks, or the percona tools as recommended int he install document. i can't see anything i missed in the installation documents. any advice would be greatly appreciated.



Subject: Thanks to Jan for leading me
Author: [Not Specified]
Posted: 2015-05-07 07:12

Thanks to Jan for leading me in the direction to solve this issue. I'm not sure if this is normal operation or not, but my docker configuration, found at \etc\default\docker on ubuntu 14, required that i have the zenoss host set as a dns server, as well as one of my actual dns servers. then to be safe I also added the --ip-forward=true (should be default) to the DOCKER_OPTS line. name resolution via zenoss contain now appears to work normally.



< Previous
Zenoss 5 stuck in "Stopping"
  Next
unable to access control center on fresh install
>