but you wouldn't find that in search without knowing the answer, which is a TXT query to
.
and then verifying Google ownership of the resulting IP address at
https://gwhois.org/74.125.177.72 (however that test is not as spoof-proof as Check My DNS) and the TXT query may return cached results for up to a minute, so the EDNS Client Subnet data may be wrong.
If you are using dig:
If you are using Google Public DNS
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32653
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; ANSWER SECTION:
If you are not using Google Public DNS
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50328
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
If you are using nslookup (Windows, mostly):
If you are using Google Public DNS
$ nslookup -q=TXT test.dns.google.com
Server: 127.0.1.1
Address: 127.0.1.1#53
Non-authoritative answer:
test.dns.google.com text = "Thanks for using Google Public DNS."
Authoritative answers can be found from:
If you are not using Google Public DNS
$ nslookup -q=TXT test.dns.google.com 4.2.2.1
Server: 4.2.2.1
Address: 4.2.2.1#53
** server can't find test.dns.google.com: NXDOMAIN