Hello Apache builds, We (Apache Qpid) have been seeing a test fail on the Ubuntu Jenkins slaves since August 9th. The test verifies the behaviour of the code when the user specifies a hostname that does not exist in DNS. For this purpose, the test uses a random name 'hg3sgaaw4lgihjs' (without hierarchal part) which is assumed not resolve. This test is longstanding and has been running on the slaves for many years without issue.
Between August 9th and 10th, something appears to have changed on the slaves, which is meaning that the lookup of the name is now returning an IP. This is causing the Java test to fail. I've investigated by introducing shell commands into the job, and can see evidence of the same problem at the UNIX level. I am certainly seeing this on slaves ubuntu4 through ubuntu6. $ host hg3sgaaw4lgihjs hg3sgaaw4lgihjs has address 198.105.244.11 hg3sgaaw4lgihjs has address 198.105.254.11 Host hg3sgaaw4lgihjs not found: 3(NXDOMAIN) $ host hg3sgaaw4lgihjs2 hg3sgaaw4lgihjs2 has address 198.105.244.11 hg3sgaaw4lgihjs2 has address 198.105.254.11 Host hg3sgaaw4lgihjs2 not found: 3(NXDOMAIN) I considered changing the test to use a RFC-2606 Reserved Top Level DNS Names hg3sgaaw4lgihjs.invalid but I notice that it too is resolving to 198.105.244.11 too. The fact that an .invalid address is resolving makes me suspect there is an environmental problem at the root cause. host hg3sgaaw4lgihjs.invalid hg3sgaaw4lgihjs.invalid has address 198.105.244.11 hg3sgaaw4lgihjs.invalid has address 198.105.254.11 Host hg3sgaaw4lgihjs.invalid not found: 3(NXDOMAIN) Is there a name resolution issue affecting these hosts? Example job affected by the issue: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-JDK1.8/ Kind regards, Keith Wall.
