Comment 4 for bug 1742420

Hi,
unfortunately that doesn't solve problem.
I have added "--insecure-bind-address=127.0.0.1" to /etc/kubernetes/apiserver and rebooted all master nodes.

coredns is in semi-working state:

192.168.3.110 - [31/Jan/2018:10:37:18 +0000] "AAAA IN harping-swan-redis. udp 36 false 512" SERVFAIL qr,rd,ra 36 2.559159ms
192.168.3.110 - [31/Jan/2018:10:37:18 +0000] "A IN harping-swan-redis. udp 36 false 512" SERVFAIL qr,rd,ra 36 2.825283ms
192.168.3.110 - [31/Jan/2018:10:37:18 +0000] "AAAA IN harping-swan-redis. udp 36 false 512" SERVFAIL qr,rd,ra 36 2.570759ms
192.168.3.110 - [31/Jan/2018:10:37:18 +0000] "A IN harping-swan-redis. udp 36 false 512" SERVFAIL qr,rd,ra 36 2.817016ms
E0131 10:37:18.376444 6 reflector.go:214] github.com/coredns/coredns/vendor/k8s.io/client-go/1.5/tools/cache/reflector.go:109: Failed to list *api.Service: the server has asked for the client to provide credentials (get services)
E0131 10:37:18.376558 6 reflector.go:214] github.com/coredns/coredns/vendor/k8s.io/client-go/1.5/tools/cache/reflector.go:109: Failed to list *api.Namespace: the server has asked for the client to provide credentials (get namespaces)
E0131 10:37:18.377639 6 reflector.go:214] github.com/coredns/coredns/vendor/k8s.io/client-go/1.5/tools/cache/reflector.go:109: Failed to list *api.Endpoints: the server has asked for the client to provide credentials (get endpoints)

If some additional steps or tests are needed let me know.