DNS audit for cdn101.com created on 2026-07-19 22:34:52

PDF

1. Name servers

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

pns41.cloudns.net
pns42.cloudns.net
pns43.cloudns.net
pns44.cloudns.net

Result: 4 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 cdn101.com.

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA

pns41.cloudns.net [185.136.96.79] (2ms):

pns42.cloudns.net [185.136.97.79] (1ms):

pns43.cloudns.net [185.136.98.79] (1ms):

pns44.cloudns.net [185.136.99.79] (1ms):

pns41.cloudns.net [185.136.96.79] (0ms):

pns42.cloudns.net [185.136.97.79] (92ms):

pns43.cloudns.net [185.136.98.79] (0ms):

pns44.cloudns.net [185.136.99.79] (0ms):

pns41.cloudns.net [185.136.96.79] (4ms):

pns42.cloudns.net [185.136.97.79] (0ms):

pns43.cloudns.net [185.136.98.79] (4ms):

pns44.cloudns.net [185.136.99.79] (0ms):

Result: The NS records returned by the DNS servers are not the same as the name servers set at the parent server.
Recommendation: Check the synchronization between the DNS servers. Returned NS records must be exactly the same as these returned by the parent server.

3. SOA record

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

San Francisco, US

pns41.cloudns.net [185.136.96.79] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns42.cloudns.net [185.136.97.79] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns43.cloudns.net [185.136.98.79] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns44.cloudns.net [185.136.99.79] (1ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

Sydney, AU

pns41.cloudns.net [185.136.96.79] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns42.cloudns.net [185.136.97.79] (133ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns43.cloudns.net [185.136.98.79] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns44.cloudns.net [185.136.99.79] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

Johannesburg, ZA

pns41.cloudns.net [185.136.96.79] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns42.cloudns.net [185.136.97.79] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns43.cloudns.net [185.136.98.79] (4ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

pns44.cloudns.net [185.136.99.79] (0ms):
undefined.localhost. support.localhost. 2020053101 7200 3600 1209600 120

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 cdn101.com

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

San Francisco, US Sydney, AU Johannesburg, ZA

pns41.cloudns.net [185.136.96.79] (1ms):
127.0.0.1

pns42.cloudns.net [185.136.97.79] (1ms):
127.0.0.1

pns43.cloudns.net [185.136.98.79] (1ms):
127.0.0.1

pns44.cloudns.net [185.136.99.79] (1ms):
127.0.0.1

pns41.cloudns.net [185.136.96.79] (0ms):
127.0.0.1

pns42.cloudns.net [185.136.97.79] (133ms):
127.0.0.1

pns43.cloudns.net [185.136.98.79] (1ms):
127.0.0.1

pns44.cloudns.net [185.136.99.79] (1ms):
127.0.0.1

pns41.cloudns.net [185.136.96.79] (0ms):
127.0.0.1

pns42.cloudns.net [185.136.97.79] (0ms):
127.0.0.1

pns43.cloudns.net [185.136.98.79] (0ms):
127.0.0.1

pns44.cloudns.net [185.136.99.79] (4ms):
127.0.0.1

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

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

San Francisco, US Sydney, AU Johannesburg, ZA

pns41.cloudns.net [185.136.96.79] (1ms):
127.0.0.1

pns42.cloudns.net [185.136.97.79] (1ms):
127.0.0.1

pns43.cloudns.net [185.136.98.79] (1ms):
127.0.0.1

pns44.cloudns.net [185.136.99.79] (1ms):
127.0.0.1

pns41.cloudns.net [185.136.96.79] (0ms):
127.0.0.1

pns42.cloudns.net [185.136.97.79] (93ms):
127.0.0.1

pns43.cloudns.net [185.136.98.79] (0ms):
127.0.0.1

pns44.cloudns.net [185.136.99.79] (1ms):
127.0.0.1

pns41.cloudns.net [185.136.96.79] (4ms):
127.0.0.1

pns42.cloudns.net [185.136.97.79] (0ms):
127.0.0.1

pns43.cloudns.net [185.136.98.79] (4ms):
127.0.0.1

pns44.cloudns.net [185.136.99.79] (0ms):
127.0.0.1

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 11.08ms.
Recommendation: The name servers have good response time.

Blog | Cloud DNS
Sponsored by ClouDNS