-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Marc,
Marc Lehmann wrote: > a) it doesn't support cname-to-cname (which is illegal, but unfortunately, > with google relying on it, there is little to do) - so cname resolution > has to be done manually (which is possible). cname-to-cname is legal (RFC1034) says 'fairly long chains' are legal. I know, because I also wrote an (async supporting) DNS lib, libunbound. It does DNSSEC validation too, so it is not in the embeddable, very tiny, space of DNS (stub-)resolvers being discussed. > b) it seemingly lacks support for ipv6, but in fact, it fully supports > ipv6 (you just have to know how dns works...) If only more people did :-) > c) like many other "asynchronous resolvers" it is of course fully synchronous > and even blockign when it has to fall back to e.g. virtual circuit mode > (for large replies). this is not uncommon. At least I did this right ... Best regards, Wouter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm/i/wACgkQkDLqNwOhpPht1gCgiTFofmFbf+/Hojt01TeLNfJO 3eMAoIhX/tGP4BsIcwRsD3lkld7wUPWF =MuGS -----END PGP SIGNATURE----- _______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
