watchNS/filesend.toについて、ここに記述してください。

NSの整合性に問題がある。内容はしらない。-- ToshinoriMaeno 2016-09-02 00:22:47

%dnsq ns filesend.to tonic.to 

2 filesend.to:
148 bytes, 1+0+4+1 records, response, noerror
query: 2 filesend.to
authority: filesend.to 86400 NS ns1.filesend.to
authority: filesend.to 86400 NS ns2.inetvass.com
authority: filesend.to 86400 NS ns-1916.awsdns-47.co.uk
authority: filesend.to 86400 NS ns1.inetvass.com
additional: ns1.filesend.to 86400 A 219.127.203.30

%dnsq ns filesend.to ns-1916.awsdns-47.co.uk 

2 filesend.to:
169 bytes, 1+4+0+0 records, response, authoritative, noerror
query: 2 filesend.to
answer: filesend.to 172800 NS ns-1238.awsdns-26.org
answer: filesend.to 172800 NS ns-1916.awsdns-47.co.uk
answer: filesend.to 172800 NS ns-314.awsdns-39.com
answer: filesend.to 172800 NS ns-949.awsdns-54.net

%dnsq ns filesend.to ns1.filesend.to 

2 filesend.to:
111 bytes, 1+3+0+1 records, response, authoritative, noerror
query: 2 filesend.to
answer: filesend.to 300 NS ns1.inetvass.com
answer: filesend.to 300 NS ns2.inetvass.com
answer: filesend.to 300 NS ns1.filesend.to
additional: ns1.filesend.to 300 A 219.127.203.30

%dnsq ns filesend.to ns1.inetvass.com 

2 filesend.to:
143 bytes, 1+3+0+3 records, response, authoritative, noerror
query: 2 filesend.to
answer: filesend.to 300 NS ns2.inetvass.com
answer: filesend.to 300 NS ns1.inetvass.com
answer: filesend.to 300 NS ns1.filesend.to
additional: ns1.filesend.to 300 A 219.127.203.30
additional: ns1.inetvass.com 10800 A 210.158.68.168
additional: ns2.inetvass.com 10800 A 210.158.68.170

$dnsq any filesend.to ns1.filesend.to 

255 filesend.to:
1183 bytes, 1+22+0+17 records, response, authoritative, noerror
query: 255 filesend.to
answer: filesend.to 300 16 Dgoogle-site-verification=5Lm52q9t9BiW1uCgBsU5eX6M5QUl15hT2Mo_iAyjbdE
answer: filesend.to 300 16 \006v=spf1,\040ip4:219.127.203.0/27\040ip4:219.127.203.192/27\024\040ip4:122.1.96.112/28\026\040ip4:119.245.228.64/29\026\040ip4:218.251.65.128/29\251\040ip4:54.92.10.105\040ip4:54.92.16.11\040ip4:54.92.31.182\040ip4:54.92.52.243\040ip4:54.92.52.247\040ip4:54.92.53.169\040ip4:54.92.53.217\040ip4:54.92.53.218\040ip4:54.92.53.223\040ip4:54.92.53.225\022\040ip4:54.186.57.104\022\040ip4:52.42.139.183\005\040~all
answer: filesend.to 300 SOA ns1.filesend.to hostmaster.filesend.to 2016072901 3600 600 1209600 300
answer: filesend.to 300 NS ns1.inetvass.com
answer: filesend.to 300 NS ns2.inetvass.com
answer: filesend.to 300 NS ns1.filesend.to
answer: filesend.to 300 MX 30 web5.filesend.to
answer: filesend.to 300 MX 30 web6.filesend.to
answer: filesend.to 300 MX 30 web7.filesend.to
answer: filesend.to 300 MX 30 web8.filesend.to
answer: filesend.to 300 MX 30 web9.filesend.to
answer: filesend.to 300 MX 30 web10.filesend.to
answer: filesend.to 300 MX 30 web11.filesend.to
answer: filesend.to 300 MX 30 web12.filesend.to
answer: filesend.to 300 MX 30 web13.filesend.to
answer: filesend.to 300 MX 30 web14.filesend.to
answer: filesend.to 300 MX 30 web15.filesend.to
answer: filesend.to 300 MX 30 web16.filesend.to
answer: filesend.to 300 MX 10 web1.filesend.to
answer: filesend.to 300 MX 20 web3.filesend.to
answer: filesend.to 300 MX 30 web2.filesend.to
answer: filesend.to 300 MX 30 web4.filesend.to
additional: ns1.filesend.to 300 A 219.127.203.30
additional: web1.filesend.to 300 A 122.1.96.113
additional: web3.filesend.to 300 A 219.127.203.7
additional: web2.filesend.to 300 A 122.1.96.114
additional: web4.filesend.to 300 A 122.1.96.117
additional: web5.filesend.to 300 A 219.127.203.9
additional: web6.filesend.to 300 A 113.38.238.30
additional: web7.filesend.to 300 A 219.127.203.195
additional: web8.filesend.to 300 A 119.245.228.212
additional: web9.filesend.to 300 A 119.245.228.67
additional: web10.filesend.to 300 A 119.245.228.69
additional: web11.filesend.to 300 A 119.245.228.68
additional: web12.filesend.to 300 A 219.127.203.197
additional: web13.filesend.to 300 A 122.1.96.118
additional: web14.filesend.to 300 A 218.251.65.130
additional: web15.filesend.to 300 A 218.251.65.131
additional: web16.filesend.to 300 A 218.251.65.132