1.3.0

Bug Fixes

• Fixed a bug with non-empty OPT records, see #51 and #55.
  This should fix all those parser errors which were reported by different users using the mongodb C# driver on certain Azure clusters!
• Fixed one native path in NameServer.ResolveNameServersNative which did not filter site local addresses properly.

New Features

• New Configuration API which will replace the property setters on the LookupClient in a future version. The current properties are marked obsolete for now.
  See #33 for more details.
• Added maximum cache duration setting (#48)
• Auto detect network name server changes (#66). If LookupClient has to discover the NameServers automatically, it now will try to react to changes in the network configuration (especially useful in long running services)
• New setting ContinueOnEmptyResponse (#64).
  This is enabled per default and instructs LookupClient to query all configured DNS server until the question is answered or no more servers are available.
• Improved EDNS handling (#61, #62).
  New settings to disable or configure the EDNS behavior of LookupClient
• Logging and Tracing and better error handling in general (#60)
• Changed the behavior when LookupClient gets a bad truncated responses, it now tries to re-run the query over TCP if it detects such cases - see #52
• Changed the result of the ResolveService APIs to include weight and order of the SRV records (#34)

Other Changes

• Added a lot more unit tests and also tests to validate backward compatibility down to the 1.1.0 API
• Changed the caching mechanism to cache only answered responses.
• Changed caching to not cache by server