1. pc.moppy.jp の Aレコードを求める。
- qname minimisation は使わないとしての追跡
一見、問題はないように見える。
1.0.1. watchA
JPへの問い合わせ:
%dig pc.moppy.jp @a.dns.jp ~/dnsq/0123/aws ; <<>> DiG 9.12.1 <<>> pc.moppy.jp @a.dns.jp ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39672 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 2b9074fbbc2db177df75b07b5e2bad215dc63323646c1c80 (good) ;; QUESTION SECTION: ;pc.moppy.jp. IN A ;; AUTHORITY SECTION: moppy.jp. 86400 IN NS ns-393.awsdns-49.com. moppy.jp. 86400 IN NS ns-1057.awsdns-04.org. moppy.jp. 86400 IN NS ns-1733.awsdns-24.co.uk. moppy.jp. 86400 IN NS ns-1626.awsdns-11.co.uk. ;; Query time: 7 msec ;; SERVER: 203.119.1.1#53(203.119.1.1) ;; WHEN: Sat Jan 25 11:51:13 JST 2020 ;; MSG SIZE rcvd: 206
1.1. moppy NS
%dig pc.moppy.jp @ns-1626.awsdns-11.co.uk. ~/dnsq/0123/aws ; <<>> DiG 9.12.1 <<>> pc.moppy.jp @ns-1626.awsdns-11.co.uk. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62655 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;pc.moppy.jp. IN A ;; AUTHORITY SECTION: pc.moppy.jp. 300 IN NS ns-1057.awsdns-04.org. pc.moppy.jp. 300 IN NS ns-1733.awsdns-24.co.uk. pc.moppy.jp. 300 IN NS ns-393.awsdns-49.com. pc.moppy.jp. 300 IN NS ns-838.awsdns-40.net. ;; Query time: 9 msec ;; SERVER: 205.251.198.90#53(205.251.198.90) ;; WHEN: Sat Jan 25 11:49:37 JST 2020 ;; MSG SIZE rcvd: 180
1.2. pc
A の値は変更されている。
pc.moppy.jp. 60 IN A 122.212.71.238 pc.moppy.jp. 60 IN A 203.136.16.182
history
%dig pc.moppy.jp @ns-393.awsdns-49.com. ~/dnsq/0123/aws ; <<>> DiG 9.12.1 <<>> pc.moppy.jp @ns-393.awsdns-49.com. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30324 ;; flags: qr aa; QUERY: 1, ANSWER: 6, AUTHORITY: 4, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;pc.moppy.jp. IN A ;; ANSWER SECTION: pc.moppy.jp. 60 IN A 122.212.71.233 pc.moppy.jp. 60 IN A 122.212.71.231 pc.moppy.jp. 60 IN A 122.212.71.234 pc.moppy.jp. 60 IN A 122.212.71.228 pc.moppy.jp. 60 IN A 122.212.71.232 pc.moppy.jp. 60 IN A 122.212.71.236 ;; AUTHORITY SECTION: pc.moppy.jp. 172800 IN NS ns-1057.awsdns-04.org. pc.moppy.jp. 172800 IN NS ns-1733.awsdns-24.co.uk. pc.moppy.jp. 172800 IN NS ns-393.awsdns-49.com. pc.moppy.jp. 172800 IN NS ns-838.awsdns-40.net. ;; Query time: 110 msec ;; SERVER: 205.251.193.137#53(205.251.193.137) ;; WHEN: Sat Jan 25 11:53:45 JST 2020 ;; MSG SIZE rcvd: 276
1.3. history
こんな返答が返る。
%dig -t ns moppy.jp @ns-393.awsdns-49.com. ~/dnsq/0123/aws ; <<>> DiG 9.12.1 <<>> -t ns moppy.jp @ns-393.awsdns-49.com. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 34229 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;moppy.jp. IN NS ;; Query time: 110 msec ;; SERVER: 205.251.193.137#53(205.251.193.137) ;; WHEN: Sat Jan 25 11:55:57 JST 2020 ;; MSG SIZE rcvd: 26
1.4. mx
$ dig -t mx pc.moppy.jp @ns-393.awsdns-49.com. ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> -t mx pc.moppy.jp @ns-393.awsdns-49.com. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53007 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;pc.moppy.jp. IN MX ;; AUTHORITY SECTION: pc.moppy.jp. 900 IN SOA ns-1733.awsdns-24.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 ;; Query time: 108 msec ;; SERVER: 205.251.193.137#53(205.251.193.137) ;; WHEN: Thu Jan 02 10:30:29 JST 2020 ;; MSG SIZE rcvd: 127