summaryrefslogtreecommitdiffstats
path: root/roles/openshift_node_dnsmasq/files
Commit message (Collapse)AuthorAgeFilesLines
* Simplify generation of /etc/origin/node/resolv.confScott Dodson2017-07-261-11/+18
| | | | | | | | Don't attempt to copy /etc/resolv.conf whenever there's no watermark, just write out the list of nameservers that network manager tells us about like we do for origin-upstream-dns.conf Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1474707
* Prevent the script to use default route ip as upstream nameserver.Steve Teuber2017-06-301-1/+2
|
* Run dns on the node and use that for dnsmasqScott Dodson2017-06-301-3/+8
|
* Push to the registry via dnsScott Dodson2017-06-181-0/+3
| | | | | | Configures OPENSHIFT_DEFAULT_REGISTRY=docker-registry.default.svc Adds 'cluster.local' to dns search on nodes via dispatcher script Adds '.svc' to NO_PROXY defaults
* node_dnsmasq - restart dnsmasq if it's not currently runningScott Dodson2016-12-051-0/+4
| | | | | Fixes Bug 1401425 Fixes BZ1401425
* openshift_node_dnsmasq - Remove strict-order option from dnsmasqScott Dodson2016-12-011-1/+0
| | | | | | | | | | | strict-order forces dnsmasq to iterate through nameservers in order. If one of the nameservers is down this will slow things down while dnsmasq waits for a timeout. Also, this option prevents dnsmasq from querying other nameservers if the first one returns a negative result. While I think it's odd to have a nameserver that returns negative results for a query that another returns positive results for this does seem to fix the issue in testing. Fixes Bug 1399577
* Set nameservers on DHCPv6 eventAlex Lossent2016-11-231-1/+1
| | | | | | A dhcp6-change event may happen on nodes running dual stack IPv4/IPv6 and DHCP, even if Openshift itself doesn't use IPv6. /etc/resolv.conf needs be adjusted as well in this case.
* Create the file in two passes, atomicly copy it overScott Dodson2016-11-181-6/+8
|
* node_dnsmasq -- Set dnsmasq as our only nameserverScott Dodson2016-11-171-1/+4
|
* Only restart dnsmasq if the DNS servers have changedTim Bielawa2016-11-011-6/+41
|
* - Prevent the script to override n number of the time the same nameserverIshentRas2016-06-131-2/+5
| | | | - Prevent the script to echo blank values from IP4_NAMESERVERS variable
* Use grep to decide when to add our commentScott Dodson2016-05-261-1/+4
| | | | | | According to the man page for resolv.conf # needs to be in the first collumn in order to start a comment. While this didn't seem to affect glibc's resolver it did really confuse the kubelet which parses the host's resolv.conf
* Removed the echo line and replaced it with inline comment. To keep ↵Jonas Nordell2016-05-231-2/+1
| | | | 99-origin-dns.sh from adding a new line in /etc/resolv.conf everytime the NetworkManager dispatcher script is executed.
* Sync comments with origin prScott Dodson2016-05-121-4/+6
|
* Use IP4_NAMESERVERS rather than DHCP4_DOMAIN_NAME_SERVERSScott Dodson2016-05-121-3/+4
| | | | | Only modify resolv.conf if IP4_NAMESERVERS is defined, it's not safe to do so otherwise.
* listen on all interfacesScott Dodson2016-05-021-1/+0
|
* Add openshift_node_dnsmasqScott Dodson2016-04-191-0/+55