Michael Conrad

:update: Development here is mostly complete. It will be a non-breaking change in 1.3.0! see #57

That's a bug in dotnet core which should be fixed in .net core 2.0... Just have to find time to target netstandard2.0 for this lib one day...

The next version will have a netstandard2.0 target, Maybe those things will be fixed. Anyways, even if it is not fixed, you'll have to work around by determine the DNS...

ok, that's unfortunate. I'll reopen the issue for tracking. Not sure if I can do anything to fix it though... DnsClient should work though when you don't use "autodiscovery" of...

Sorry for the late reply. I actually had a feature to dis-/en-able servers over time, basically disabling a server from the list of servers if it returns certain errors and...

Yeah we could add that as an additional configuration. Sounds reasonable.

@AlexLaroche sorry for the very late reply, but you can actually build your own recursive resolver with this library and by using just one client instance, using the QueryServer APIs....

Each type has specific properties which are parsed and populated by this library. You're supposed to use those instead of parsing a string or binary data yourself. Depending on the...

Well, the returned value of `ToString` might also change in future version. There is no type safe guarantee that the returned value will be the same format or order of...

I don't really get what you mean with value only. Most resource records have many different fields (not just one value). Others have lists of strings or binary data, enum...