<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Per request, I have attached the DNSStuff report.</div><div><br></div><div>We are also looking into the zone to make sure that all is configured properly.</div><br><table align="CENTER" border="1" cellpadding="2" width="100%"><tbody><tr style="font-size: small;"><th style="min-width: 8%;" align="CENTER" bgcolor="#dddddd" width="8%">Category</th><th style="min-width: 5%;" align="CENTER" bgcolor="#dddddd" width="5%">Status</th><th align="CENTER" bgcolor="#dddddd" width="15%">Test Name</th><th align="CENTER" bgcolor="#dddddd">Information</th></tr>
<tr><td rowspan="5" style="min-width: 8%;" width="8%">Parent</td> <td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Missing Direct Parent check</td><td>OK.
Your direct parent zone exists, which is good. Some domains (usually
third or fourth level domains, such as <a href="http://example.co.us">example.co.us</a>) do not have a
direct parent zone ('co.us' in this example), which is legal but can
cause confusion.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="BLACK"><b>INFO</b></font></td><td width="15%">NS records at parent servers</td><td>Your NS records at the parent servers are:<br><br><div class="code"><a href="http://ns1.comsiteconstruction.com">ns1.comsiteconstruction.com</a>. [216.132.149.46] [TTL=172800] [US]<br>
<a href="http://ns2.comsiteconstruction.com">ns2.comsiteconstruction.com</a>. [216.132.149.47] [TTL=172800] [US]<br>
<a href="http://ns3.comsiteconstruction.com">ns3.comsiteconstruction.com</a>. [206.135.249.30] [TTL=172800] [US]<br>
</div>[These were obtained from c.gtld-servers.net]</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Parent nameservers have your nameservers listed</td><td>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.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Glue at parent nameservers</td><td>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.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">DNS servers have A records</td><td>OK.
All your DNS servers either have A records at the zone parent servers,
or do not need them (if the DNS servers are on other TLDs). A records
are required for your hostnames to ensure that other DNS servers can
reach your DNS servers. Note that there will be problems if your DNS
servers do not have these same A records.</td></tr>
</tbody></table>
<table align="CENTER" border="1" cellpadding="2" width="100%"><tbody><tr><td rowspan="19" style="min-width: 8%;" width="8%">NS</td> <td style="min-width: 6%;" align="CENTER" width="6%"><font color="BLACK"><b>INFO</b></font></td><td width="15%">NS records at your nameservers</td><td>Your NS records at your nameservers are:<br><br><div class="code">[None of your nameservers returned your NS records; they could be down
or unreachable, or could all be lame nameservers]</div>
</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Open DNS servers</td><td>OK.
Your DNS servers do not announce that they are open DNS servers.
Although there is a slight chance that they really are open DNS servers,
this is very unlikely. Open DNS servers increase the chances that of
cache poisoning, can degrade performance of your DNS, and can cause your
DNS servers to be used in an attack (so it is good that your DNS
servers do not appear to be open DNS servers).
</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Mismatched glue</td><td>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.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">No NS A records at nameservers</td><td>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.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" bgcolor="YELLOW" width="6%"><font color="BLACK"><b>WARN</b></font></td><td width="15%">All nameservers report identical NS records</td><td>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).<br><br>
<div class="code">216.132.149.46 returns 0 answers (may be a referral)<br>
216.132.149.47 returns 0 answers (may be a referral)<br>
206.135.249.30 returns 0 answers (may be a referral)<br>
</div></td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">All nameservers respond</td><td>OK. All of your nameservers listed at the parent nameservers responded.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Nameserver name validity</td><td>OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Number of nameservers</td><td>OK. You have 3 nameservers. You must have at least 2 nameservers (<a href="http://www.dnsstuff.com/dnsmedia/rfcs/rfc2182.txt">RFC2182</a> section 5 recommends at least 3 nameservers), and preferably no more than 7.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" bgcolor="RED" width="6%"><b>FAIL</b></td><td width="15%"><font color="BLACK"><b>Lame nameservers</b></font></td><td>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: <br>216.132.149.46<br>216.132.149.47<br>206.135.249.30<br>
</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Missing (stealth) nameservers</td><td>OK. All 0 of your nameservers (as reported by your nameservers) are also listed at the parent servers.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" bgcolor="RED" width="6%"><b>FAIL</b></td><td width="15%"><font color="BLACK"><b>Missing nameservers 2</b></font></td><td>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:<br><a href="http://ns1.comsiteconstruction.com">ns1.comsiteconstruction.com</a>.<br><a href="http://ns2.comsiteconstruction.com">ns2.comsiteconstruction.com</a>.<br><a href="http://ns3.comsiteconstruction.com">ns3.comsiteconstruction.com</a>.<br>
</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">No CNAMEs for domain</td><td>OK. There are no CNAMEs for <a href="http://comsiteconstruction.com">comsiteconstruction.com</a>. <a href="http://www.dnsstuff.com/dnsmedia/rfcs/rfc1912.txt">RFC1912</a> 2.4 and <a href="http://www.dnsstuff.com/dnsmedia/rfcs/rfc2181.txt">RFC2181</a> 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.<!-- Note that I only checked comsiteconstruction.com, I did not check the NS records, which should not have CNAMEs either.--></td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">No NSs with CNAMEs</td><td>OK. There are no CNAMEs for your NS records. <a href="http://www.dnsstuff.com/dnsmedia/rfcs/rfc1912.txt">RFC1912</a> 2.4 and <a href="http://www.dnsstuff.com/dnsmedia/rfcs/rfc2181.txt">RFC2181</a> 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Nameservers on separate class C's</td><td>OK.
You have nameservers on different Class C (technically, /24) IP
ranges. You must have nameservers at geographically and topologically
dispersed locations. <a href="http://www.dnsstuff.com/dnsmedia/rfcs/rfc2182.txt">RFC2182</a> 3.1 goes into more detail about secondary nameserver location.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">All NS IPs public</td><td>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.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">TCP Allowed</td><td>OK.
All your DNS servers allow TCP connections. Although rarely used, TCP
connections are occasionally used instead of UDP connections. When
firewalls block the TCP DNS connections, it can cause hard-to-diagnose
problems.</td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="BLACK"><b>INFO</b></font></td><td width="15%">Nameservers versions</td><td>Your nameservers have the following versions:<br><br>216.132.149.46: "100.100.100"<br>216.132.149.47: "100.100.100"<br>206.135.249.30: "100.100.100"<br></td></tr>
<tr><td style="min-width: 6%;" align="CENTER" width="6%"><font color="GREEN"><b>PASS</b></font></td><td width="15%">Stealth NS record leakage</td><td>Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.</td></tr>
</tbody></table><table align="CENTER" border="1" cellpadding="2" width="100%"><tbody><tr><td rowspan="1" style="min-width: 8%;" width="8%">SOA</td> <td style="min-width: 6%;" align="CENTER" bgcolor="RED" width="6%"><b>FAIL</b></td><td width="15%"><font color="BLACK"><b>SOA Record</b></font></td><td>No valid SOA record came back:<br> is not <a href="http://comsiteconstruction.com">comsiteconstruction.com</a>.</td></tr></tbody></table><div><br></div><div>
<span class="Apple-style-span" style="font-family: Helvetica; "><div><br class="Apple-interchange-newline">Kind regards,</div><div><br><div><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><font class="Apple-style-span" face="Verdana" size="3"><span class="Apple-style-span" style="font-size: 12px; "><font class="Apple-style-span" size="2"><span class="Apple-style-span" style="font-size: 10px; ">Titus Bolton<br>Antenna Systems & Solutions, Inc.<br>931 Albion Avenue<br>Schaumburg, Illinois 60193-4550<br>United States of America<br>Phone: +1-847-584-1000 Fax: +1-847-584-9951<br><a href="http://www.antennasystems.com/">http://www.antennasystems.com</a><br> <br>GSA Contract Number: GS-35F-0479T <br>Electronic Counter Measures, Trap and Trace Devices, and accessories.<br> <br>Watch our network broadcast television interviews on <a href="http://www.youtube.com/antennasystems">www.youtube.com/antennasystems</a><br> <br><b><i>Confidentiality note</i></b><i>: <br>This message is the property of Antenna Systems & Solutions, Inc. and contains information which may be privileged or confidential. It is meant only for the intended recipients and/or their authorized agents. If you believe you have received this message in error, please notify us immediately by return e-mail and destroy any printed or electronic copies of this message. Any unauthorized use, dissemination, disclosure, or copying of this message or the information contained in it, is strictly prohibited and may be unlawful. Thank you for your cooperation</i>.</span></font></span></font><br></span></div><div><font class="Apple-style-span" face="Verdana" size="2"><span class="Apple-style-span" style="font-size: 10px; "><br></span></font></div></div></span><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br><div><div>On Jan 3, 2011, at 9:37 AM, Chris Gebhardt - VIRTBIZ Internet wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Titus Bolton wrote:<br><blockquote type="cite">First and foremost, hello all and Snappy Snew Year.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Has anyone had any problems with lame name servers on BQ/BO?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If anyone has had experience in resolving this type of issue I would <br></blockquote><blockquote type="cite">love to hear about it. I can provide information needed. One of the <br></blockquote><blockquote type="cite">domains that we're having issues with is <a href="http://comsiteconstruction.com">comsiteconstruction.com</a> <br></blockquote><blockquote type="cite"><<a href="http://comsiteconstruction.com">http://comsiteconstruction.com</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> From DNSStuff we're getting these three failures:<br></blockquote><blockquote type="cite">Lame Nameservers (they don't answer authoritatively for the domain)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Missing Nameservers 2<br></blockquote><blockquote type="cite"><a href="http://ns1.comsiteconstruction.com">ns1.comsiteconstruction.com</a> <<a href="http://ns1.comsiteconstruction.com">http://ns1.comsiteconstruction.com</a>><br></blockquote><blockquote type="cite"><a href="http://ns2.comsiteconstruction.com">ns2.comsiteconstruction.com</a> <<a href="http://ns2.comsiteconstruction.com">http://ns2.comsiteconstruction.com</a>><br></blockquote><blockquote type="cite"><a href="http://ns3.comsiteconstruction.com">ns3.comsiteconstruction.com</a> <<a href="http://ns3.comsiteconstruction.com">http://ns3.comsiteconstruction.com</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">SOA Record: No valid SOA came back.<br></blockquote><br>Sounds to me like you don't have the DNS zone set correctly. Make sure <br>you have the domain configured in DNS and you have the SOA correctly set <br>with the primary and secondary nameserver fields filled out.<br>-- <br>Chris Gebhardt<br>VIRTBIZ Internet Services<br>Access, Web Hosting, Colocation, Dedicated<br><a href="http://www.virtbiz.com">www.virtbiz.com</a> | toll-free (866) 4 VIRTBIZ<br>_______________________________________________<br>Blueonyx mailing list<br><a href="mailto:Blueonyx@blueonyx.it">Blueonyx@blueonyx.it</a><br>http://www.blueonyx.it/mailman/listinfo/blueonyx<br></div></blockquote></div><br></body></html>