There is one by djb: http://dnscurve.org/
OpenDNS implemented it in 2010 (they call their implementation DNSCrypt, it usually requires an OS extension)
OpenBSD accepts a "tcp" option in the /etc/resolv.conf file in order to force connections to use TCP so that they can easily be tunneled over SSH.
The popular Unbound caching resolver can communicate over SSL to an upstream resolver, and there is even a nice GUI: dnssec-trigger. NLNet provides a public resolver that of course supports this protocol.
dnscurve is a protocol for authenticating and encrypting data between an authoritative server and a resolver.
dnscrypt is a different protocol (although partly based on the same crypto primitives as dnscurve) for authenticating and encrypting data between a resolver and a client.
OpenDNS implemented dnscurve in 2010, and dnscrypt in 2011.
All these protocols have issues in the real world, due to routers and firewalls intercepting DNS traffic, and dropping encrypted queries. Some broken devices and resolvers are even breaking DNSSEC (stripping records), but this is far less common.
A workaround is to use a different port and protocol, typically TCP port 443. Or to use encapsulation in TXT records, which has different issues.
dnscrypt's successor, called dnssig, is also being worked on in order to always offer authentication, and optional encryption.
In a simple sense, only the host name and IP address are not protected.
---
ORIGINAL: I have a question about the security of the button, though I may be wrong. The outgoing request is a GET with the credit card info in plain-text as a query parameter. With it went all of the cookies in the origin's domain.
GET https://api.stripe.com/v1/tokens?key=W1xyC0XilnJTkz52noGj1Hh...
The SSL keeps the cookies safe from loggers, but not from stripe. The URL, however, is not protected from anybody, right?