No, I’ve discovered the openshift_use_dnsmasq=False ansible option and now is the openshift DNS the one listening on port 53, but seems still not accessible from our domain controller as an standard DNS server, so I’ve resigned from this and using a wildcard DNS entry that at least allow me to progress.
Javier Palacios De: Aleksandar Lazic [mailto:[email protected]] Hi Javier. Please can you tell us if your issue is now solved? Best Regards Aleks on Dienstag, 06. Juni 2017 at 19:32 was written: Ah I think I got you now. The proxy mode is the default mode for dnsmasq. http://www.thekelleys.org.uk/dnsmasq/doc.html Cite from website. .... The DNS subsystem provides a local DNS server for the network, with forwarding of all query types to upstream recursive DNS servers and caching of common record types .... Regards Aleks Javier Palacios <[email protected]<mailto:[email protected]>> schrieb am 06.06.2017: For this you will need to add the cluster.local<http://cluster.local> domain into the DNS Server which is configured in the client and forward the requests to dnsmasq. I think you need something like this called split horizon. https://serverfault.com/a/563397/391298 That is exactly my question, which is much simpler than the serverfault question & answer, as I don't want to override any authoritative answers, just to get them. What I would do is the following. .) add cluster.local<http://cluster.local> zone in your primary dns server .) point the ns entries for master01 In particular, how to do this two steps at least, that I know how to do for standard dnsmasq as authoritative server, but not as "proxy" for the openshift one. Javier Palacios -- ME2Digital e. U. https://me2digital.online/
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
