Thus said Alexei Malinin on Fri, 05 Dec 2014 15:49:59 +0300: > - the question is - how and with what tools (dig, host, nslookup, or > maybe C or Perl libs) can I verify the NS glue records in the parent > zone of my ISP (zone transfers are denied)?
The entries in the ADDITIONAL SECTION below are ``glue records'' for the NS records in the ANSWER SECTION. The problem you have, however, DNS resolvers are going to have to make a lot of additional DNS requests to be able to determine if the glue can be used. For the glue to be immediately trusted, it would have to be in-bailiwick (e.g. ns1.0-15.66.233.212.in-addr.arpa and ns2.0-15.66.233.212.in-addr.arpa). But, At any rate, there you have it, glue is found in the ADDITIONAL SECTION: $ dig ptr 1.0-15.66.233.212.in-addr.arpa @ns1.agtel.net ; <<>> DiG 9.4.2-P2 <<>> ptr 1.0-15.66.233.212.in-addr.arpa @ns1.agtel.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37069 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 7 ;; QUESTION SECTION: ;1.0-15.66.233.212.in-addr.arpa. IN PTR ;; ANSWER SECTION: 1.0-15.66.233.212.in-addr.arpa. 43200 IN PTR dynamic-212-233-66-1.amt.ru. ;; AUTHORITY SECTION: 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns58-cloud.nic.ru. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns1.agtel.net. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns2.agtel.net. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns4-l5.nic.ru. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns8-l5.nic.ru. 0-15.66.233.212.in-addr.arpa. 43200 IN NS ns54-cloud.nic.ru. ;; ADDITIONAL SECTION: ns1.agtel.net. 600 IN A 212.111.64.132 ns2.agtel.net. 600 IN A 212.233.88.2 ns4-l5.nic.ru. 25082 IN A 91.217.20.13 ns8-l5.nic.ru. 36736 IN A 91.217.21.13 ns54-cloud.nic.ru. 19033 IN A 195.253.64.16 ns54-cloud.nic.ru. 19033 IN AAAA 2a01:5b0:4::10 ns58-cloud.nic.ru. 12582 IN A 195.253.65.16 ;; Query time: 273 msec ;; SERVER: 212.111.64.132#53(212.111.64.132) ;; WHEN: Sun Dec 7 23:03:49 2014 ;; MSG SIZE rcvd: 354 Andy -- TAI64 timestamp: 4000000054854018
