GamingOnDemand
07-17-2005, 01:38
I ahve set my name servers up and get a bunch of fails and a few warns. Any help would be appreciated
Please click here to see what the fails and warns are http://dnsreport.com/tools/dnsreport.ch?domain=gamingondemand.net
Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:
ns1.gamingondemand.net. [66.90.103.155] [TTL=172800] [US]
ns2.gamingondemand.net. [67.159.7.137] [TTL=172800] [US]
[These were obtained from m.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
NS INFO NS records at your nameservers Your NS records at your nameservers are:
[None of your nameservers returned your NS records; they could be down
or unreachable, or could all be lame nameservers]
PASS Mismatched glue OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
PASS No NS A records at nameservers OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
WARN All nameservers report identical NS records WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).
66.90.103.155 returns 0 answers (may be a referral)
67.159.7.137 returns 0 answers (may be a referral)
PASS All nameservers respond OK. All of your nameservers listed at the parent nameservers responded.
PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASS Number of nameservers OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
FAIL Lame nameservers 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:
66.90.103.155
67.159.7.137
PASS Missing (stealth) nameservers OK. All 0 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
FAIL Missing nameservers 2 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:
ns1.gamingondemand.net.
ns2.gamingondemand.net.
PASS No CNAMEs for domain OK. There are no CNAMEs for gamingondemand.net. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS Nameservers on separate class C's OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
INFO Nameservers versions Your nameservers have the following versions:
66.90.103.155: "9.2.5"
67.159.7.137: "9.2.5"
PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.
SOA INFO SOA record Your SOA record [TTL=0] is:
Primary nameserver:
Hostmaster E-mail address:
Serial #: 0
Refresh: 0
Retry: 0
Expire: 0
Default TTL: 0
FAIL NS agreement on SOA Serial # ERROR: Your nameservers disagree as to which version of your DNS is the latest (4294967295 versus 0). This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 0 is the correct serial #. The serial numbers reported by each DNS server are:
FAIL SOA MNAME Check ERROR: Your SOA (Start of Authority) record states that your master (primary) name server is: . However, that is not a valid domain name!
FAIL SOA RNAME Check ERROR: Your SOA (Start of Authority) record states that your DNS contact E-mail address in hostname format is: . However, that is NOT valid (it must have at least 2 '.''s in it and no '@')!
WARN SOA Serial Number WARNING: Your SOA serial number is: 0. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.
FAIL SOA REFRESH value WARNING: Your SOA REFRESH interval is : 0 seconds. This seems very low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
FAIL SOA RETRY value WARNING: Your SOA RETRY interval is : 0 seconds. This seems very low. You should consider increasing this value to about 120-7200 seconds. The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
FAIL SOA EXPIRE value WARNING: Your SOA EXPIRE time is : 0 seconds. This seems very low. You should consider increasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
FAIL SOA MINIMUM TTL value WARNING: Your SOA MINIMUM TTL is : 0 seconds. This seems very low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
MX FAIL MX Category ERROR: I couldn't find any MX records for gamingondemand.net. If you want to receive E-mail on this domain, you should have MX record(s). Without any MX records, mailservers should attempt to deliver mail to the A record for gamingondemand.net. I can't continue in a case like this, so I'm assuming you don't receive mail on this domain.
Mail FAIL Connect to mail servers ERROR: I could not find any mailservers for gamingondemand.net.
WWW FAIL WWW Category ERROR: I couldn't find any A records for www.gamingondemand.net. If you want a website at www.gamingondemand.net, you will need an A record for www.gamingondemand.net. If you do not want a website at www.gamingondemand.net, you can ignore this error.
Legend:
* Rows with a FAIL indicate a problem that in most cases really should be fixed.
* Rows with a WARN indicate a possible minor problem, which often is not worth pursuing.
* Note that all information is accessed in real-time (except where noted), so this is the freshest information about your domain.
Please click here to see what the fails and warns are http://dnsreport.com/tools/dnsreport.ch?domain=gamingondemand.net
Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:
ns1.gamingondemand.net. [66.90.103.155] [TTL=172800] [US]
ns2.gamingondemand.net. [67.159.7.137] [TTL=172800] [US]
[These were obtained from m.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
NS INFO NS records at your nameservers Your NS records at your nameservers are:
[None of your nameservers returned your NS records; they could be down
or unreachable, or could all be lame nameservers]
PASS Mismatched glue OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
PASS No NS A records at nameservers OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
WARN All nameservers report identical NS records WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).
66.90.103.155 returns 0 answers (may be a referral)
67.159.7.137 returns 0 answers (may be a referral)
PASS All nameservers respond OK. All of your nameservers listed at the parent nameservers responded.
PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASS Number of nameservers OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
FAIL Lame nameservers 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:
66.90.103.155
67.159.7.137
PASS Missing (stealth) nameservers OK. All 0 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
FAIL Missing nameservers 2 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:
ns1.gamingondemand.net.
ns2.gamingondemand.net.
PASS No CNAMEs for domain OK. There are no CNAMEs for gamingondemand.net. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS Nameservers on separate class C's OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
INFO Nameservers versions Your nameservers have the following versions:
66.90.103.155: "9.2.5"
67.159.7.137: "9.2.5"
PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.
SOA INFO SOA record Your SOA record [TTL=0] is:
Primary nameserver:
Hostmaster E-mail address:
Serial #: 0
Refresh: 0
Retry: 0
Expire: 0
Default TTL: 0
FAIL NS agreement on SOA Serial # ERROR: Your nameservers disagree as to which version of your DNS is the latest (4294967295 versus 0). This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 0 is the correct serial #. The serial numbers reported by each DNS server are:
FAIL SOA MNAME Check ERROR: Your SOA (Start of Authority) record states that your master (primary) name server is: . However, that is not a valid domain name!
FAIL SOA RNAME Check ERROR: Your SOA (Start of Authority) record states that your DNS contact E-mail address in hostname format is: . However, that is NOT valid (it must have at least 2 '.''s in it and no '@')!
WARN SOA Serial Number WARNING: Your SOA serial number is: 0. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.
FAIL SOA REFRESH value WARNING: Your SOA REFRESH interval is : 0 seconds. This seems very low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
FAIL SOA RETRY value WARNING: Your SOA RETRY interval is : 0 seconds. This seems very low. You should consider increasing this value to about 120-7200 seconds. The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
FAIL SOA EXPIRE value WARNING: Your SOA EXPIRE time is : 0 seconds. This seems very low. You should consider increasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
FAIL SOA MINIMUM TTL value WARNING: Your SOA MINIMUM TTL is : 0 seconds. This seems very low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
MX FAIL MX Category ERROR: I couldn't find any MX records for gamingondemand.net. If you want to receive E-mail on this domain, you should have MX record(s). Without any MX records, mailservers should attempt to deliver mail to the A record for gamingondemand.net. I can't continue in a case like this, so I'm assuming you don't receive mail on this domain.
Mail FAIL Connect to mail servers ERROR: I could not find any mailservers for gamingondemand.net.
WWW FAIL WWW Category ERROR: I couldn't find any A records for www.gamingondemand.net. If you want a website at www.gamingondemand.net, you will need an A record for www.gamingondemand.net. If you do not want a website at www.gamingondemand.net, you can ignore this error.
Legend:
* Rows with a FAIL indicate a problem that in most cases really should be fixed.
* Rows with a WARN indicate a possible minor problem, which often is not worth pursuing.
* Note that all information is accessed in real-time (except where noted), so this is the freshest information about your domain.