Try this command to find out all the related Google DNS services:
host -a dns.google.
For Cloudflare, try
host one.one.one.one.
We all know about the public DNS services offered by Google (8.8.8.8, 8.8.4.4) and Cloudflare (1.1.1.1, 1.0.0.1); did you know these addresses
have names as well? And of course there are IPv6 addresses to go with
the IPv4 ones.
Try this command to find out all the related Google DNS services:
host -a dns.google.
That’s quite a breathtaking list of entries.
Lawrence D'Oliveiro wrote:
host -a dns.google.
joerg@jazz:~$ host -a dns.google
Trying "dns.google"
Host dns.google not found: 4(NOTIMP)
We all know about the public DNS services offered by Google (8.8.8.8, 8.8.4.4) and Cloudflare (1.1.1.1, 1.0.0.1); did you know these
addresses have names as well? And of course there are IPv6 addresses to
go with the IPv4 ones.
Try this command to find out all the related Google DNS services:
host -a dns.google.
(Yup, that’s “dns.google.”, no “.com” or anything else on the end.) That’s quite a breathtaking list of entries.
For Cloudflare, try
host one.one.one.one.
Note that the “-a” option (“tell me everything”) doesn’t work with Cloudflare; quite a few online services are now imposing restrictions
on these “all info” lookups, but clearly not Google, at least not on
this domain: obviously they want it to remain easy for people to
discover the services they’re offering.
'host' is not recognized as an internal or external command,
operable program or batch file.
(On Windows 11)
I did write “dns.google.”, did I not?
joerg@jazz:~$ host -a dns.google
Trying "dns.google"
Host dns.google not found: 4(NOTIMP)
I did write “dns.google.”, did I not?
We all know about the public DNS services offered by Google (8.8.8.8, 8.8.4.4) and Cloudflare (1.1.1.1, 1.0.0.1); did you know these
addresses have names as well? And of course there are IPv6 addresses
to go with the IPv4 ones.
Lawrence D'Oliveiro wrote:
I did write “dns.google.”, did I not?
It works with nslookup, though
joerg@jazz:~$ nslookup dns.google.
Server: 192.168.1.18
Address: 192.168.1.18#53
Non-authoritative answer:
Name: dns.google
Address: 8.8.8.8
Name: dns.google
Address: 8.8.4.4
Name: dns.google
Address: 2001:4860:4860::8844
Name: dns.google
Address: 2001:4860:4860::8888
-jw-
Lawrence D'Oliveiro wrote:
joerg@jazz:~$ host -a dns.google
Trying "dns.google"
Host dns.google not found: 4(NOTIMP)
I did write “dns.google.”, did I not?
That's what the system changed it to before actually issuing the
command.
joerg@jazz:~$ host -a dns.google.
Trying "dns.google"
Host dns.google not found: 4(NOTIMP)
(On Windows 11)
use nslookup instead
Andy Burns wrote:
use nslookup instead
Doesn’t seem to have the equivalent of the “-a” option of host.
host -a dns.google. | grep -c '^dns'
26
I get 26 lines of info; how many lines do you get?
the "host -a" seems to rely on the DNS server supporting queries over
TCP as well as UDP, my Draytek router only supports UDP
Andy Burns wrote:
the "host -a" seems to rely on the DNS server supporting queries over
TCP as well as UDP, my Draytek router only supports UDP
Try going direct.
On Mon, 2 Sep 2024 01:51:38 -0000 (UTC), I wrote:
Try this command to find out all the related Google DNS services:
host -a dns.google.
That’s quite a breathtaking list of entries.
Anyone spotted the easter egg yet?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 403 |
Nodes: | 16 (2 / 14) |
Uptime: | 40:21:27 |
Calls: | 8,407 |
Calls today: | 2 |
Files: | 13,171 |
Messages: | 5,904,811 |