DNSMasq occasionally delays short name resolutions by 15-20 seconds

Solution Verified - Updated -


DNSMasq occasionally has issues with 15-20 second delayed short-name resolution on Worker and Infra node(s).

$ nslookup sub
;; connection timed out; no servers could be reached

@dcona07l ~] $ nslookup sub.example.domain
Server:         10.x.x.x
Address:        10.x.x.x#53

Name:   sub.example.domain
Address: 10.x.x.y

Restarting the DNSMasq service is a workaround


OpenShift Container Platform 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content