Hi, On 12/07 09:22, Chris Lamb wrote: > Whilst varnish-modules builds successfully on unstable/amd64, according to > Debian Policy 4.9 packages may not attempt network access during > a build. > > 00:00:00.000000 IP e66b957b9098.60905 > > sitecomwlr1000.sitecomwlr1000.domain: 10880+ A? phk.freebsd.dk. (32) > 00:00:00.000060 IP e66b957b9098.60905 > > sitecomwlr1000.sitecomwlr1000.domain: 24843+ AAAA? phk.freebsd.dk. (32) > 00:00:00.001007 IP e66b957b9098.54550 > > sitecomwlr1000.sitecomwlr1000.domain: 27794+ A? phk.freebsd.dk. (32) > 00:00:00.001044 IP e66b957b9098.54550 > > sitecomwlr1000.sitecomwlr1000.domain: 39210+ AAAA? phk.freebsd.dk. (32) > 00:00:00.001129 IP e66b957b9098.45718 > > sitecomwlr1000.sitecomwlr1000.domain: 14444+ A? phk.freebsd.dk. (32) > 00:00:00.001152 IP e66b957b9098.45718 > > sitecomwlr1000.sitecomwlr1000.domain: 3037+ AAAA? phk.freebsd.dk. (32) > > [..]
This is because of varnishtest trying to resolve phk.freebsd.dk every time it is invoked to check if DNS works: https://github.com/varnishcache/varnish-cache/blob/master/bin/varnishtest/vtc_main.c#L616 We need to either patch varnishtest and hardcode feature_dns, or avoid running the tests altogether.