Hi Tapani,

it shouldn't since "transparent" still forwards missing records, so the mx problem would apply only if a A record is defined for the domain itself.

Ref: https://linux.die.net/man/5/unbound.conf

transparent

If there is a match from local data, the query is answered. Otherwise if the query has a different name, the query is resolved normally. If the query is for a name given in localdata but no such type of data is given in localdata, then a noerror nodata answer is returned. If no local-zone is given local-data causes a transparent zone to be created by default.

Since "transparent" is the implicit default i believe it was the actual type until  version 143, when typetransparent was specified (see https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=1b6b8d97aac8a8056a4ef5c9d571a1947551e17f;hp=e4013c9dabd55f399b57939a4ad9b5192aac8077), so this is a rollback more than a patch.

Moreover the side effect is not just an annoyance: as an example I use chieck_mk to monitor all nodes in my network and one of the default check is the ability to resolve local names. With typetransparent the result of the check (which is native, not implemented by me) is detected as a failure in name resolution both on linux and windows targets.

I agree that we are discussing a very specific subject, but it seems to me that it should be best to stick with the default or have a very stong point (which IMHO is missing in this case) to use a different directive.

Best regards,

Giovanni