nslookup/dig/host commands querying local bind takes more time to resolve domain names with edns?

Solution Verified - Updated -

Issue

  • nslookup/dig/host commands querying local bind takes more time to resolve domain names with edns?
[root@test ]$ tshark -r client.pcap -Y 'ip.addr == XX.XX.XX.41 && udp.port == 53' 
  329  74.467439 XX.XX.XX.41 → XX.XX.XX3.100 DNS 91 Standard query 0x7f0e A example.com.com OPT
  333  76.467732 XX.XX.XX.41 → XX.XX.XX1.100 DNS 91 Standard query 0x2e6a A example.com.com OPT
  340  78.468044 XX.XX.XX.41 → XX.XX.XX2.100 DNS 91 Standard query 0xae18 A example.com.com OPT
  342  80.468224 XX.XX.XX.41 → XX.XX.XX4.100 DNS 91 Standard query 0x1fcb A example.com.com OPT
  399  92.873695 XX.XX.XX.41 → XX.XX.XX3.100 DNS 91 Standard query 0x6073 A example.com.com OPT
  416  94.874021 XX.XX.XX.41 → XX.XX.XX1.100 DNS 80 Standard query 0xc8ed A example.com.com <<< 

Environment

  • Red Hat Enterprise Linux 6
  • Latest bind
  • Bind configured to forward dns server not supporting edns

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.