QuicksearchEntry's LinksReferring links
easyDNS Main LinksCategoriesStaff WeblogseasyDNS Member Blogs» SelfEmployment.ca
» Jim Carroll » Efficient Market Canada » CEO Blog - Time Leadership by Jim Estill » Caught In Between by Lawrence Greene Archives |
Monday, February 13. 2006NS6 added to nameserver clusterTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Dnsreports is stating that the sixth nameserver is lame for
my domain name (antihotmail.com). What does this mean? http://www.dnsreport.com ---------------------------------------------------------- delegations for antihotmail.com ns1.easydns.com. [216.220.40.243] [TTL=172800] [CA] ns2.easydns.com. [209.200.151.4] [TTL=172800] [US] remote1.easydns.com. [209.200.131.4] [TTL=172800] [US] remote2.easydns.com. [205.210.42.20] [TTL=172800] [CA] remote3.easydns.com. [209.200.131.10] [TTL=172800] [US] ns6.easydns.net. [72.32.5.211] [TTL=172800] [US] [These were obtained from m.gtld-servers.net] ---------------------------------------------------------- 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: 72.32.5.211 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: remote3.easydns.com. ns6.easydns.net.
Hello John,
At this time, it appears that "dnsreport.com" is properly reporting back that "ns6.easydns.net" is not a lame server: =-=-=-=-= PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain. =-=-=-=-= As "ns6.easydns.net" is relatively new, it's possible that for a time it was not answering authoritatively, rather, grabbing the information from our other nameservers and reporting back as a non-authoritative nameserver. This is not presently the case. =-=-=-=-= 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: ns6.easydns.net. remote3.easydns.com. =-=-=-=-= This error above is due to the fact that while you may have delegated your domain to all six of our nameservers, the NS records within your zone file still only have four of our nameservers: ns1.easydns.com ns2.easydns.com remote1.easydns.com remote2.easydns.com If your zone file hasn't been regenerated in a while (which appears to be the case with your domain "antihotmail.com"), then "remote3.easydns.com" and "ns6.easydns.net" wouldn't appear in your NS records, as we recently made a change to our system to have those added when creating an updated zone file for your domain. Simply log into your account, and make a trivial change to your domain (such as changing the minimum time in your SOA to something else, and then back again), and the missing two nameservers will be added. As always, if we can be of any further assistance, please do not hesitate to email us as "support@easydns.com". Regards, Evan.
Mark:
My domain has always been using the .easydns.COM dns servers. I now notice that there's a whole slew more ending with .NET, among those the new ns6. # for i in ns1 ns2 ns3 ns4 ns5 ns6 ns7 remote1 remote2 remote3 remote4 remote5 remote6;do host $i.easydns.com ;host $i.easydns.net;done |grep -v NXDOMAIN ns1.easydns.com has address 216.220.40.243 ns1.easydns.net has address 205.210.42.21 ns2.easydns.com has address 209.200.151.4 ns2.easydns.net has address 205.210.42.22 ns3.easydns.com has address 216.235.9.10 ns6.easydns.net has address 72.32.5.211 remote1.easydns.com has address 209.200.131.4 remote1.easydns.net has address 208.247.106.167 remote2.easydns.com has address 205.210.42.20 remote2.easydns.net has address 198.96.119.44 remote3.easydns.com has address 209.200.131.10 remote4.easydns.com has address 65.75.128.178 I'm not concerned about the redundancy, EasyDNS has that taken care of in all aspects. The DNS servers are: - geographically separated; - connected to diverse upstream bandwidth providers; - hosted with different, respected providers; and - protected by a variety of DDoS mitigation solutions. As such, my question is merely based on curiousity.
the easydns.net servers (the only one that is valid for the moment
is ns6.easydns.net) are provided in the event that there is a collosal failure within the easydns.com namespace, or even the .com gTLD namespace at VeriSign. (Which still leaves the .net at VeriSign, but we do what we can So instead of having all of our nameservers residing under a .com, we have at least one under a .net, shielding our entire nameserver cluster from being "taken out" via some misadventure at the registry level, etc. Ideally we'd like to have more diversity in this respect, going forward. Future nameservers may take advantage of easydns.ca or easydns.org.
Now I'm confused...
If there is only one valid .net server, why are all of the others showing up at all?
Hi Charles.
Some of the others were used in staging environments or in stand-by backup servers, none of those records are live in any registries. The .net for ns6 is the first step in a move toward diversifying the nameserver cluster out of a single TLD. I hope this helps.
I added remote3.easydns.com and ns6.easydns.net to the DNS list for my domain (schmidtzone.com), but now dnsreport.com is giving me two failing marks ("Missing (stealth) nameservers" and "Stealth NS record leakage").
I briefly perturbed my SOA as in comment #1.1, but it didn't help. Is something misconfigured somewhere or is the failing mark given out inappropriately? --Christopher
dig is coming out with ns6.easydns.com
even dnsstuff.com is coming with stealth server ns6.easydns.COM can you verify the information with your FAQ, should it be .COM and not ns6.easydns.net |
easyDNS CEO Mark Jeftovic's BlogRunning an affiliate program? Don't pay for sales you already had in the bag
Wednesday, August 27. 2008 The Long Tail of Entitlement Trumps Self-Reliance and Intelligence Tuesday, August 5. 2008 TM-Collection - The latest "Trademark Directory" scam outfit Thursday, July 31. 2008 Ten Years of easyDNS Thursday, July 31. 2008 DNS cache poisoning exploit released Wednesday, July 23. 2008 .ME Top Level Domain launch indicative of new TLD rollouts Thursday, July 17. 2008 .ME Top Level Domain launch indicative of new TLD rollouts Thursday, July 17. 2008 Life as a lemming Friday, July 11. 2008 I once was lost, but now I'm found Tuesday, July 8. 2008 Tucows may be overlooked as a value stock (no, really) Monday, July 7. 2008 What is wrong with this picture? Friday, June 6. 2008 Ontario Energy Savings or Ontario Energy Slamming? Wednesday, June 4. 2008 Newsflash: Some Web 2.0 Companies are Over Valued Tuesday, June 3. 2008 What would Eckhart Tolle do with incontrovertible proof that 9/11 was an "inside job"? Friday, May 30. 2008 The CRTC Gets a Clue... Tuesday, May 13. 2008 |