Browse Source

Disable negative caching, set cache TTL to 1s

When running headless services as pods on OpenShift, no ClusterIP is
assigned. In these cases, peer pods are relying on DNS to locate the
service endpoints. When a pod is deleted or another trigger causes the
endpoint to change, the OpenShift DNS is updated immediately. However,
dnsmasq has a default TTL of 30s, so the wrong response is returned
on name resolution. Removing negative caching and turning the TTL to
a very short 1s should resolve the issue.

Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
Steve Kuznetsov 7 năm trước cách đây
mục cha
commit
d04cf6b2ae
1 tập tin đã thay đổi với 2 bổ sung0 xóa
  1. 2 0
      roles/openshift_node_dnsmasq/templates/origin-dns.conf.j2

+ 2 - 0
roles/openshift_node_dnsmasq/templates/origin-dns.conf.j2

@@ -1,3 +1,5 @@
 no-resolv
 domain-needed
 server=/{{ openshift.common.dns_domain }}/{{ openshift.common.kube_svc_ip }}
+no-negcache
+max-cache-ttl=1