fokinewjersey.blogg.se

Etunes lk audio
Etunes lk audio










etunes lk audio
  1. #Etunes lk audio serial number#
  2. #Etunes lk audio serial#
etunes lk audio

Your SOA EXPIRE number is: 1209600.Looks ok

#Etunes lk audio serial#

Your SOA serial appears to be the number of seconds since midnight when the last DNS change was made. The recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. That server is listed at the parent servers.

#Etunes lk audio serial number#

All your nameservers agree that your SOA serial number is 1. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.

etunes lk audio

It seems you are safe from a single point of failure. This is a good thing and useful even if UDP connections are used by default. Seems all your DNS servers allow TCP connections. This is a good thing because it will prevent DNS delays and other problems like Looks like the IP addresses of your nameservers are public. Looks like you have nameservers on different subnets! RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. All nameservers returned by the parent server c.nic.lk are the same as the ones reported by your nameservers. Missing nameservers reported by your nameservers All NS records are the same at the parent and at your nameservers. All the nameservers listed at the parent servers answer authoritatively for your domain. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. All of the NS records that your nameservers report seem valid. All nameservers listed at the parent server responded. The NS records at all your nameservers are identical. You can fix this for example by adding A records to your nameservers for the zones listed above. INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. If there are any missing or stealth nameservers you should see them below! This tests only nameservers that are common at the parent and at your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. NS records got from your nameservers listed at the parent NS are: This happens a lot if you have nameservers on different TLD ( for example with nameserver ns.) It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. The parent nameserver c.nic.lk is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers. The parent server c.nic.lk has your nameservers listed. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check. Good. c.nic.lk, the parent server I interrogated, has information for your TLD. Nameserver records returned by the parent servers are:Ĭ.nic.lk was kind enough to give us that information.












Etunes lk audio