动态域名解析

ripple0328

已经把域名服务器指向DNSPARK的那个了，
客户端用的DDCLINT
还是不行，想查一下问题出在哪一部
用DNSstuff查了一下，做了个报告，有很多看不懂，请帮我看一下，可能是那部出现问题了？

ripple0328

报告是个表格，不知道则么上传阿，直接复制上太乱了

ripple0328

WARNING. The parent servers (I checked with cns.cernet.net.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.

这个好像没关系

ripple0328

ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
69.0.220.85
69.59.153.140
64.34.197.141
83.170.90.100
66.98.161.195

ripple0328

ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns4.dnspark.net.
ns5.dnspark.net.
ns1.dnspark.net.
ns2.dnspark.net.
ns3.dnspark.net.

ripple0328

WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Class C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.

ripple0328

后面几条是什么问题呢？