I just released a 0.6 version of my Resolver library. This release fixes one bug related to UFFI usage. For some reason the bug did not show itself on SBCL or CMUCL, but somebody found it while looking to port the code to another CL implementation. The biggest user-visible change is that the library now uses keyword symbols for all resource record types and other constants in the interface. So, instead of

(lookup "findinglisp.com" 'mx)

you now say

(lookup "findinglisp.com" :mx)

and the answer comes back as

((53369 T :QUERY NIL NIL T T :NO-ERROR 1 2 2 6) (("findinglisp.com." :MX :IN))
 (("findinglisp.com." :MX :IN 86178 10 "mx01.1and1.com.")
  ("findinglisp.com." :MX :IN 86178 10 "mx00.1and1.com."))
 (("findinglisp.com." :NS :IN 172578 "ns27.1and1.com.")
  ("findinglisp.com." :NS :IN 172578 "ns28.1and1.com."))
 (("mx01.1and1.com." :A :IN 83865 #(217 160 230 13))
  ("mx01.1and1.com." :A :IN 83865 #(217 160 230 11))
  ("mx00.1and1.com." :A :IN 1237 #(217 160 230 10))
  ("mx00.1and1.com." :A :IN 1237 #(217 160 230 12))
  ("ns27.1and1.com." :A :IN 77450 #(217 160 224 3))
  ("ns28.1and1.com." :A :IN 32577 #(217 160 228 3))))