Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #255994
| From | local10 <local10@tutanota.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out |
| Date | 2023-03-13 21:00 +0100 |
| Message-ID | <G8WuR-cgnu-3@gated-at.bofh.it> (permalink) |
| References | <G8JxD-c8pY-1@gated-at.bofh.it> <G8RbP-cdfn-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Mar 13, 2023, 14:11 by casey@deccio.net: > Based on what I saw in the logs, your resolver is having trouble reaching the internet. It shows problems with both the priming query (./NS) and the trust query (./DNSKEY). Could you try running the following? > > $ dig +norec @198.41.0.4 . NS > $ dig +norec @2001:503:ba3e::2:30 . NS > $ dig +norec @198.41.0.4 . DNSKEY > $ dig +norec @2001:503:ba3e::2:30 . DNSKEY > > These manually send the same queries to the internet that your resolver is attempting. > > Cheers, > Casey > $ dig +norec @198.41.0.4 . NS ; <<>> DiG 9.18.12-1-Debian <<>> +norec @198.41.0.4 . NS ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19016 ;; flags: qr aa; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 27 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 518400 IN NS e.root-servers.net. . 518400 IN NS h.root-servers.net. . 518400 IN NS l.root-servers.net. . 518400 IN NS i.root-servers.net. . 518400 IN NS a.root-servers.net. . 518400 IN NS d.root-servers.net. . 518400 IN NS c.root-servers.net. . 518400 IN NS b.root-servers.net. . 518400 IN NS j.root-servers.net. . 518400 IN NS k.root-servers.net. . 518400 IN NS g.root-servers.net. . 518400 IN NS m.root-servers.net. . 518400 IN NS f.root-servers.net. ;; ADDITIONAL SECTION: e.root-servers.net. 518400 IN A 192.203.230.10 e.root-servers.net. 518400 IN AAAA 2001:500:a8::e h.root-servers.net. 518400 IN A 198.97.190.53 h.root-servers.net. 518400 IN AAAA 2001:500:1::53 l.root-servers.net. 518400 IN A 199.7.83.42 l.root-servers.net. 518400 IN AAAA 2001:500:9f::42 i.root-servers.net. 518400 IN A 192.36.148.17 i.root-servers.net. 518400 IN AAAA 2001:7fe::53 a.root-servers.net. 518400 IN A 198.41.0.4 a.root-servers.net. 518400 IN AAAA 2001:503:ba3e::2:30 d.root-servers.net. 518400 IN A 199.7.91.13 d.root-servers.net. 518400 IN AAAA 2001:500:2d::d c.root-servers.net. 518400 IN A 192.33.4.12 c.root-servers.net. 518400 IN AAAA 2001:500:2::c b.root-servers.net. 518400 IN A 199.9.14.201 b.root-servers.net. 518400 IN AAAA 2001:500:200::b j.root-servers.net. 518400 IN A 192.58.128.30 j.root-servers.net. 518400 IN AAAA 2001:503:c27::2:30 k.root-servers.net. 518400 IN A 193.0.14.129 k.root-servers.net. 518400 IN AAAA 2001:7fd::1 g.root-servers.net. 518400 IN A 192.112.36.4 g.root-servers.net. 518400 IN AAAA 2001:500:12::d0d m.root-servers.net. 518400 IN A 202.12.27.33 m.root-servers.net. 518400 IN AAAA 2001:dc3::35 f.root-servers.net. 518400 IN A 192.5.5.241 f.root-servers.net. 518400 IN AAAA 2001:500:2f::f ;; Query time: 43 msec ;; SERVER: 198.41.0.4#53(198.41.0.4) (UDP) ;; WHEN: Mon Mar 13 15:54:28 EDT 2023 ;; MSG SIZE rcvd: 811 # Note that I'm running bind with "-4" option, that is, IPv4 only $ dig +norec @2001:503:ba3e::2:30 . NS ;; UDP setup with 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30) for . failed: network unreachable. ;; UDP setup with 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30) for . failed: network unreachable. ;; UDP setup with 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30) for . failed: network unreachable. $ dig +norec @198.41.0.4 . DNSKEY ; <<>> DiG 9.18.12-1-Debian <<>> +norec @198.41.0.4 . DNSKEY ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60299 ;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1472 ;; QUESTION SECTION: ;. IN DNSKEY ;; ANSWER SECTION: . 172800 IN DNSKEY 256 3 8 AwEAAcVnO2jZFx4756Rb/yAhJnsl72eemsObU43nclmXwqdJlp+kC5WQ jGYkqLT5xkaUCPhkr4NKLLrIBZXeSGazc6gx/yrrMtUpXcQvax6kfDJP Tu974OmeEbtjyyP7ZG5tUfSwNWt/4EuxDNmZTESG8jU0ZLjYIB11pK0g SXQbMVPyIyGtFGHMPx6UxWn6zUzpECWRFbqEvkA6Y13zeJ1jG2Rki/zs 7a/o13FTl/kI9013Eh6l6Kc2zxbc14GS8fpM0/xQIrZZyeiXj/2C4Rcs PeqWuNj9m0qSQrbrCZtLHb20U8x1uue4iwSX9y7LpwZd6vjYd1d6dgBa 1Xxgc/TC+m8= . 172800 IN DNSKEY 257 3 8 AwEAAaz/tAm8yTn4Mfeh5eyI96WSVexTBAvkMgJzkKTOiW1vkIbzxeF3 +/4RgWOq7HrxRixHlFlExOLAJr5emLvN7SWXgnLh4+B5xQlNVz8Og8kv ArMtNROxVQuCaSnIDdD5LKyWbRd2n9WGe2R8PzgCmr3EgVLrjyBxWezF 0jLHwVN8efS3rCj/EWgvIWgb9tarpVUDK/b58Da+sqqls3eNbuv7pr+e oZG+SrDK6nWeL3c6H5Apxz7LjVc1uTIdsIXxuOLYA4/ilBmSVIzuDWfd RUfhHdY6+cn8HFRm+2hM8AnXGXws9555KrUB5qihylGa8subX2Nn6UwN R1AkUTV74bU= ;; Query time: 151 msec ;; SERVER: 198.41.0.4#53(198.41.0.4) (UDP) ;; WHEN: Mon Mar 13 15:56:12 EDT 2023 ;; MSG SIZE rcvd: 578 $ dig +norec @2001:503:ba3e::2:30 . DNSKEY ;; UDP setup with 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30) for . failed: network unreachable. ;; UDP setup with 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30) for . failed: network unreachable. ;; UDP setup with 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30) for . failed: network unreachable. Regards,
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 07:10 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-13 07:20 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 07:40 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-13 08:30 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-13 09:30 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 09:30 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-13 09:40 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 10:20 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-13 10:40 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 11:00 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Reco <recoverym4n@enotuniq.net> - 2023-03-13 12:00 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 12:40 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Reco <recoverym4n@enotuniq.net> - 2023-03-13 13:10 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 21:00 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Reco <recoverym4n@enotuniq.net> - 2023-03-13 22:50 +0100
[SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 23:20 +0100
Re: [SOLVED?] BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Casey Deccio <casey@deccio.net> - 2023-03-13 23:30 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-13 23:30 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Greg Wooledge <greg@wooledge.org> - 2023-03-13 23:40 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-13 23:40 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-14 00:10 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Greg Wooledge <greg@wooledge.org> - 2023-03-14 00:30 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-14 00:40 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Greg Wooledge <greg@wooledge.org> - 2023-03-14 01:00 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-14 04:20 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Darac Marjal <mailinglist@darac.org.uk> - 2023-03-14 21:10 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Greg Wooledge <greg@wooledge.org> - 2023-03-14 21:30 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Jeremy Ardley <jeremy@ardley.org> - 2023-03-13 23:40 +0100
Re: [SOLVED?] Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Greg Wooledge <greg@wooledge.org> - 2023-03-13 23:40 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Michel Verdier <mv524@free.fr> - 2023-03-13 13:00 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 21:10 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Greg Wooledge <greg@wooledge.org> - 2023-03-13 12:30 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 12:40 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out Casey Deccio <casey@deccio.net> - 2023-03-13 15:20 +0100
Re: BIND: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out local10 <local10@tutanota.com> - 2023-03-13 21:00 +0100
csiph-web