I'm experiencing this as well, and can confirm this seems to be related to SELinux. Setting SELinux to permissive mode allows resolved to work correctly. I suppose the policy needs to be updated?