DNS audit for dldizhi.com created on 2026-03-17 14:44:33

PDF

1. Name servers

Name servers listed at the parent server a.gtld-servers.net:

ns1.dyna-ns.net
ns2.dyna-ns.net

Result: 2 name servers found at the parent server (set at the domain provider).
Recommendation: Everything is okay. There is more than one name server added to dldizhi.com.

2. NS records

NS records returned by each name server configured for the domain name

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA

ns1.dyna-ns.net [162.159.26.92] (172ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns1.dyna-ns.net [162.159.27.158] (192ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns2.dyna-ns.net [162.159.25.5] (91ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns2.dyna-ns.net [162.159.24.5] (91ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns1.dyna-ns.net [162.159.26.92] (27ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns1.dyna-ns.net [162.159.27.158] (23ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns2.dyna-ns.net [162.159.25.5] (78ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns2.dyna-ns.net [162.159.24.5] (77ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns1.dyna-ns.net [162.159.27.158] (151ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns1.dyna-ns.net [162.159.26.92] (151ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns2.dyna-ns.net [162.159.24.5] (244ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns2.dyna-ns.net [162.159.25.5] (2ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns1.dyna-ns.net [162.159.26.92] (348ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns1.dyna-ns.net [162.159.27.158] (348ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns2.dyna-ns.net [162.159.24.5] (216ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

ns2.dyna-ns.net [162.159.25.5] (220ms):
ns1.dyna-ns.net
ns2.dyna-ns.net

Result: The NS records returned by the DNS servers are the same as the name servers set at the parent server.
Recommendation: It is not required to do any changes. All name servers are synchronized.

3. SOA record

SOA record returned by each name server configured for the domain name

Frankfurt, DE

ns1.dyna-ns.net [162.159.27.158] (159ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns1.dyna-ns.net [162.159.26.92] (155ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns2.dyna-ns.net [162.159.24.5] (92ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns2.dyna-ns.net [162.159.25.5] (90ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

San Francisco, US

ns1.dyna-ns.net [162.159.27.158] (23ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns1.dyna-ns.net [162.159.26.92] (24ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns2.dyna-ns.net [162.159.24.5] (84ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns2.dyna-ns.net [162.159.25.5] (83ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

Sydney, AU

ns1.dyna-ns.net [162.159.26.92] (151ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns1.dyna-ns.net [162.159.27.158] (150ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns2.dyna-ns.net [162.159.24.5] (234ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns2.dyna-ns.net [162.159.25.5] (238ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

Johannesburg, ZA

ns1.dyna-ns.net [162.159.27.158] (324ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns1.dyna-ns.net [162.159.26.92] (4ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns2.dyna-ns.net [162.159.24.5] (220ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

ns2.dyna-ns.net [162.159.25.5] (4ms):
ns1.dyna-ns.net. hostmaster.dldizhi.com. 2026012002 16384 2048 1209600 300

Result: The SOA record returned by the name servers is the same on all of them.
Recommendation: It is not required to do any changes. The name servers are synchronized.

4. A record distribution by location for dldizhi.com

Shows how the name servers respond to requests for dldizhi.com

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA

ns1.dyna-ns.net [162.159.26.92] (182ms):

ns1.dyna-ns.net [162.159.27.158] (181ms):

ns2.dyna-ns.net [162.159.24.5] (90ms):

ns2.dyna-ns.net [162.159.25.5] (89ms):

ns1.dyna-ns.net [162.159.27.158] (26ms):

ns1.dyna-ns.net [162.159.26.92] (25ms):

ns2.dyna-ns.net [162.159.25.5] (84ms):

ns2.dyna-ns.net [162.159.24.5] (3ms):

ns1.dyna-ns.net [162.159.27.158] (150ms):

ns1.dyna-ns.net [162.159.26.92] (151ms):

ns2.dyna-ns.net [162.159.24.5] (243ms):

ns2.dyna-ns.net [162.159.25.5] (239ms):

ns1.dyna-ns.net [162.159.27.158] (344ms):

ns1.dyna-ns.net [162.159.26.92] (320ms):

ns2.dyna-ns.net [162.159.24.5] (216ms):

ns2.dyna-ns.net [162.159.25.5] (220ms):

5. A record distribution by location for www.dldizhi.com

Shows how the name servers respond to requests for www.dldizhi.com

Frankfurt, DE San Francisco, US Sydney, AU Johannesburg, ZA

ns1.dyna-ns.net [162.159.26.92] (180ms):

ns1.dyna-ns.net [162.159.27.158] (167ms):

ns2.dyna-ns.net [162.159.25.5] (94ms):

ns2.dyna-ns.net [162.159.24.5] (91ms):

ns1.dyna-ns.net [162.159.26.92] (26ms):

ns1.dyna-ns.net [162.159.27.158] (23ms):

ns2.dyna-ns.net [162.159.25.5] (72ms):

ns2.dyna-ns.net [162.159.24.5] (74ms):

ns1.dyna-ns.net [162.159.27.158] (149ms):

ns1.dyna-ns.net [162.159.26.92] (150ms):

ns2.dyna-ns.net [162.159.24.5] (231ms):

ns2.dyna-ns.net [162.159.25.5] (236ms):

ns1.dyna-ns.net [162.159.27.158] (340ms):

ns1.dyna-ns.net [162.159.26.92] (4ms):

ns2.dyna-ns.net [162.159.25.5] (216ms):

ns2.dyna-ns.net [162.159.24.5] (220ms):

6. Speed

Result: During the checks in the previous steps, multiple DNS requests were executed to the name servers responsible for the domain name. Average response time of the name servers is 149.88ms.
Recommendation: The name servers respond slow. Try moving to an Anycast DNS service in order to speed up the resolution of the domain name and first page load of the web site.

Newer reports for dldizhi.com: 2026-03-17 16:15:55
Blog | Cloud DNS
Sponsored by ClouDNS