DNS resolution of domain names used in PacketShaper matching rules not working

Products

• PacketShaper S-Series

Issue/Introduction

The dns names output shows lookup pending for all the domain names used for the class matching rules. It may work right after boot for some time but after 'dns refresh' it doesn't work. (This particular issue prevents proper classification and is critical).

# dns names

Domain Name                IP Address          TTL   Age RQSNCRP Error
atestProblem.com           <unknown>             0   228     02  lookup pending
testProblem.com            <unknown>             0   228     02  lookup pending
www.bluecoat.com           <unknown>             0   228     02  lookup pending
www.cisco.com              <unknown>             0   228     02  lookup pending
www.facebook.com           <unknown>             0   228     02  lookup pending
www.ge.com                 <unknown>             0   228     02  lookup pending
www.gm.com                 <unknown>             0   228     02  lookup pending
www.google.com             <unknown>             0   228     02  lookup pending
www.honda.com              <unknown>             0   228     02  lookup pending
www.mistake.com            <unknown>             0   228     02  lookup pending
www.problem123.com         <unknown>             0   228     02  lookup pending
www.toyota.com             <unknown>             0   228     02  lookup pending
www.yahoo.com              <unknown>             0   228     02  lookup pending
time.nist.gov              <unknown>             0   228     02  lookup pending
<unknown>                  10.78.52.27           0   228     02  lookup pending

While the automatic resolution and synchronization is not working, the manual lookup works just fine.

# dns lookup www.yahoo.com

Please wait, the hostname 'www.yahoo.com' is being resolved.........
lookup result:
Query:          www.yahoo.com
Canonical Name: fd-fp3.wg1.b.yahoo.com
Alias:          www.yahoo.com
Address:        206.190.36.105
Address:        206.190.36.45

Cause

The problem was due to a bug in the code, reported as a DNS resolution and synchronization issue.

Resolution

This bug has been fixed in PS 11.5.1.3. The DNS resolution and synchronization issue will no longer be a problem after upgrading to 11.5.1.3 or higher.