Hi Andreas, The default local-zone type for "localhost." changed from static to redirect, so that the default local-data applies to both localzone. and its subdomains.
You can change your local-data domain to localhost., then it will still be available under monitoring_app_test_if_unbound_is_alive.localhost, but also for localhost itself. You can also add a local-zone for monitoring_app_test_if_unbound_is_alive.localhost with the static type: local-zone: "monitoring_app_test_if_unbound_is_alive.localhost." static Regards, -- Ralph On 20-09-17 10:36, A. Schulze via Unbound-users wrote: > > W.C.A. Wijngaards via Unbound-users: > >> Unbound 1.6.6 is available: > >> Bug Fixes: >> - Redirect all localhost names to localhost address for RFC6761. > > Hello, > > I've a setup that monitor a running resolver on regular base. > To avoid the log is fooded with queries for "localhost" I found it > meaningful to monitor a more 'speaking' label: > I monitor "monitoring_app_test_if_unbound_is_alive.localhost." and > expect a A Record 127.0.0.1 > For that I've in unbound.conf: > > server: > local-data: 'monitoring_app_test_if_unbound_is_alive.localhost. A > 127.0.0.1' > local-data: 'monitoring_app_test_if_unbound_is_alive.localhost. TXT > "some description" > > After upgrading to 1.6.6 I now get errors > [1505895425] unbound-checkconf[2825:0] error: local-data in redirect > zone must reside at top of zone, not at > monitoring_app_test_if_unbound_is_alive.localhost. A 127.0.0.1 > [1505895425] unbound-checkconf[2825:0] fatal error: failed local-zone, > local-data configuration > > OK, I now could remove the "local-data: A Record" at all. But I like to > understand the feature a little more. > Could anyone explain the error message a bit more verbose? > > Thanks > Andreas
