Problem
HealthTest-ReverseZonesPresent can validate ExpectedReverseZones, but the normal built-in runner calls it without arguments.
File: health-tests/HealthTest-ReverseZonesPresent.ps1, lines 12-19.
In a normal run it only lists existing reverse zones and reports PASS, even when a required reverse zone is missing.
Simple example
The organization requires 10.in-addr.arpa, but that zone is absent. A direct parameterized call could find the problem. The built-in run receives no expected list and reports whatever zones exist as PASS.
Expected behavior
Provide a documented configuration path for the expected zones, or make the default test an honest policy inventory instead of a successful requirement check.
Acceptance criteria
- A normal run can load an expected-zone baseline.
- Missing configured zones produce findings.
- No configured baseline is not described as successful validation.
- Runner-level tests cover configured and unconfigured cases.
Problem
HealthTest-ReverseZonesPresentcan validateExpectedReverseZones, but the normal built-in runner calls it without arguments.File:
health-tests/HealthTest-ReverseZonesPresent.ps1, lines 12-19.In a normal run it only lists existing reverse zones and reports PASS, even when a required reverse zone is missing.
Simple example
The organization requires
10.in-addr.arpa, but that zone is absent. A direct parameterized call could find the problem. The built-in run receives no expected list and reports whatever zones exist as PASS.Expected behavior
Provide a documented configuration path for the expected zones, or make the default test an honest policy inventory instead of a successful requirement check.
Acceptance criteria