the current deployment of coredns instruction creates a multi-protocol loadbalancer service. based on my tests, while this is an admissible manifest in kubernetes, it does not work with metallb. Metallb is the way to create load balancer services on baremetal, which is the most common scenario or on prem deployments (when coredns would be needed).

The workaround is described here (coincidentally? with a dns service): https://metallb.io/usage/#ip-address-sharing