1. nike.co.jp
Contents
nike.comが本家で、それ以外のドメイン名は雑な管理のようだ。 ../nike.jp -- ToshinoriMaeno 2019-06-08 23:55:15
NS queryにNS返答があるが、同時にCNAMEも返してくる。
- リゾルバーはこれをどう解釈するのだろうか。
- CNAMEだけを受け入れる。8.8.8.8、1.1.1.1 (RCODE nxdomainかも)
- NS, CNAME 両方を受け入れる。9.9.9.9, unbound (RFCに反する動作)
2. whois
a. [ドメイン名] NIKE.CO.JP e. [そしきめい] かぶしきがいしゃないきじゃぱん f. [組織名] 株式会社ナイキジャパン g. [Organization] Nike Japan Corporation k. [組織種別] 株式会社 l. [Organization Type] Corporation m. [登録担当者] HH1926JP n. [技術連絡担当者] MA129JP p. [ネームサーバ] dns01.bekknet.ad.jp p. [ネームサーバ] dns02.bekknet.ad.jp s. [署名鍵] [状態] Connected (2019/12/31) [登録年月日] 1996/12/05 [接続年月日] 1996/12/13 [最終更新] 2019/01/01 01:05:23 (JST)
3. JP
%dig -t ns nike.co.jp @a.dns.jp ~/dnsq/co2019 ; <<>> DiG 9.12.1 <<>> -t ns nike.co.jp @a.dns.jp ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53133 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 454afec80cba2607fd0ae4265cfc46dae2e7c78a1d90187c (good) ;; QUESTION SECTION: ;nike.co.jp. IN NS ;; AUTHORITY SECTION: nike.co.jp. 86400 IN NS dns01.bekknet.ad.jp. nike.co.jp. 86400 IN NS dns02.bekknet.ad.jp. ;; ADDITIONAL SECTION: dns01.bekknet.ad.jp. 86400 IN A 202.235.199.100 dns02.bekknet.ad.jp. 86400 IN A 202.210.128.100 ;; Query time: 5 msec ;; SERVER: 203.119.1.1#53(203.119.1.1) ;; WHEN: Sun Jun 09 08:38:02 JST 2019 ;; MSG SIZE rcvd: 150
4. bekknet
これも奇妙な返事
%dig -t ns nike.co.jp @dns01.bekknet.ad.jp ~/dnsq/co2019 ; <<>> DiG 9.12.1 <<>> -t ns nike.co.jp @dns01.bekknet.ad.jp ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1145 ;; flags: qr aa rd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;nike.co.jp. IN NS ;; ANSWER SECTION: nike.co.jp. 600 IN NS dns01.bekknet.ad.jp. nike.co.jp. 600 IN NS dns02.bekknet.ad.jp. nike.co.jp. 600 IN CNAME cojp.nike.jp. ;; ADDITIONAL SECTION: dns01.bekknet.ad.jp. 3600 IN A 202.235.199.100 dns02.bekknet.ad.jp. 3600 IN A 202.210.128.100 ;; Query time: 16 msec ;; SERVER: 202.235.199.100#53(202.235.199.100) ;; WHEN: Sun Jun 09 08:41:24 JST 2019 ;; MSG SIZE rcvd: 135
%dig -t a cojp.nike.jp ~/dnsq/co2019 ; <<>> DiG 9.12.1 <<>> -t a cojp.nike.jp ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46898 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;cojp.nike.jp. IN A ;; Query time: 4 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Jun 09 08:42:46 JST 2019 ;; MSG SIZE rcvd: 30
5. www.nike.co.jp
$ dig -t a www.nike.co.jp @dns02.bekknet.ad.jp. ; <<>> DiG 9.14.0 <<>> -t a www.nike.co.jp @dns02.bekknet.ad.jp. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38903 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;www.nike.co.jp. IN A ;; ANSWER SECTION: www.nike.co.jp. 600 IN CNAME cojp.nike.jp. ;; AUTHORITY SECTION: nike.co.jp. 600 IN NS dns01.bekknet.ad.jp. nike.co.jp. 600 IN NS dns02.bekknet.ad.jp. ;; ADDITIONAL SECTION: dns01.bekknet.ad.jp. 3600 IN A 202.235.199.100 dns02.bekknet.ad.jp. 3600 IN A 202.210.128.100 ;; Query time: 13 msec ;; SERVER: 202.210.128.100#53(202.210.128.100) ;; WHEN: 日 6月 09 08:49:46 JST 2019 ;; MSG SIZE rcvd: 139