From Newsgroup: comp.misc

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.
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

Useful info. Thanks.
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

Lawrence D'Oliveiro wrote:

Try this command to find out all the related Google DNS services:

host -a dns.google.

joerg@jazz:~$ host -a dns.google
Trying "dns.google"
Host dns.google not found: 4(NOTIMP)

Ubuntu 22.04, btw.

For Cloudflare, try

host one.one.one.one.

This one works.

-jw-
--
And now for something completely different...
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On Mon, 2 Sep 2024 01:51:38 -0000 (UTC), Lawrence D'Oliveiro wrote:

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.

There are some more https://en.wikipedia.org/wiki/Public_recursive_name_server#Notable_public_DNS_service_operators
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On Mon, 02 Sep 2024 17:15:21 +0200, Joerg Walther wrote:

Lawrence D'Oliveiro wrote:

host -a dns.google.

joerg@jazz:~$ host -a dns.google
Trying "dns.google"
Host dns.google not found: 4(NOTIMP)

I did write “dns.google.”, did I not?
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

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?
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On 02/09/2024 02:51, Lawrence D'Oliveiro wrote:

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.

C:\Users\public>host

'host' is not recognized as an internal or external command,
operable program or batch file.

(On Windows 11)
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

SH wrote:

'host' is not recognized as an internal or external command,
operable program or batch file.

(On Windows 11)

use nslookup instead
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

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)

-jw-
--
And now for something completely different...
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

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-
--
And now for something completely different...
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On 02.09.2024 um 01:51 Uhr Lawrence D'Oliveiro wrote:

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.

Yes, but I only use them for testing.
I run my own resolver with BIND9 on my machines at home.
--
kind regards
Marco

Send spam to 1725234698muell@cartoonies.org

--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On 03/09/2024 15:11, Joerg Walther wrote:

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-

Done the nslookup command and I get:

Name: dns.google
Addresses: ::
0.0.0.0



--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On Tue, 03 Sep 2024 16:09:36 +0200, Joerg Walther wrote:

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)

Odd. Trouble with your ISP’s caching name servers?

Try specifically addressing the query to a known-good name server, e.g.

host -a dns.google. 8.8.8.8
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On Tue, 3 Sep 2024 09:30:10 +0100, Andy Burns wrote:

(On Windows 11)

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?
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

Lawrence D'Oliveiro wrote:

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?

windows
=======
C:\Users\Andy>nslookup dns.google. 192.168.1.1
Server: UnKnown
Address: 192.168.1.1

Non-authoritative answer:
Name: dns.google
Addresses: 2001:4860:4860::8844
2001:4860:4860::8888
8.8.4.4
8.8.8.8

wsl2
====

root@YogaHome:~# nslookup dns.google. 192.168.1.1
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: dns.google
Address: 8.8.4.4
Name: dns.google
Address: 8.8.8.8
Name: dns.google
Address: 2001:4860:4860::8844
Name: dns.google
Address: 2001:4860:4860::8888



the "host -a" seems to rely on the DNS server supporting queries over
TCP as well as UDP, my Draytek router only supports UDP

root@YogaHome:~# host -a dns.google. 192.168.1.1
Trying "dns.google"
Trying "dns.google"
;; Connection to 192.168.1.1#53(192.168.1.1) for dns.google. failed:
timed out.
;; no servers could be reached


Using other DNS servers which do support TCP, the amount of info
returned seems to depend on what types of RR they support, mainly DNSSEC?

root@YogaHome:~# host -a dns.google. 9.9.9.9 | wc -l
27
root@YogaHome:~# host -a dns.google. 8.8.8.8 | wc -l
42
root@YogaHome:~# host -a dns.google. 94.247.43.254 | wc -l
17


--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On Wed, 4 Sep 2024 10:19:30 +0100, 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.
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

Lawrence D'Oliveiro wrote:

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.

The outputs showing up to 42 lines of output were from when I did that,
but I have no need to know all those RRSIG/DNSKEY answers
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.misc

On Mon, 2 Sep 2024 21:54:58 -0000 (UTC), I wrote:

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?

dns.google. 300 IN TXT "https://xkcd.com/1361/"
--- Synchronet 3.20a-Linux NewsLink 1.114