Correct, the library only acts as a server at the moment. I implemented the server code according to the MDNS spec:
Implementing a resolve method would involve creating a query packet in the required format and then sending out to the multicast address used for MDNS. After sending you would wait for a response for a maximum of a few seconds, parsing any packets received. I would suggest following the rules described in https://tools.ietf.org/html/rfc6762#section-6.7 that talk about legacy resolvers - this avoids the need to register for multicast responses and handle lots of messages which are possibly not responses to your query. In legacy mode responders will send packets directly to your host via unicast.
As mentioned, there is probably a lot of re-usable code already in the library to help with creating query packets and parsing responses.