SOA Serial Number: Your SOA serial number is 1219521806. This does not match the recommended format of YYYYMMDDnn [RIPE-203]. This is not necessarily a problem as long as your DNS admin knows what they are doing. Warning
SOA Master Nameserver: Your SOA master nameserver is ns1.intellisource.ro. It is also listed at the parent nameservers. This is correct. Pass
SOA Admin Email: Your SOA admin email address is smike@intellisource.ro. This seems to be a valid email address. PassSOA Refresh: Your SOA refresh value is 3 hours. This specifies how often a slave nameserver checks for DNS updates at the master. This seems to be OK. RFC 1912 recommends values between 20 minutes and 12 hours. Pass
SOA Retry: Your SOA retry value is 60 mins. This is the time a slave nameserver will wait if an attempt to contact a primary nameserver failed before it tries again. This seems to be OK. PassSOA Expire: Your SOA expire value is 24 hours. This is how long a slave nameserver will cache data if it cannot reach the master nameserver. If your master nameserver is unreachable for longer than this your slave nameservers will no longer cache your DNS. This seems low. I would expect at least 1 week here [RIPE-203]. You should consider increasing this value. Warning
SOA Minimum TTL: Your SOA minimum TTL value is 10 hours 40 mins. This is interpreted by servers as the default TTL. It can be overridden on individual DNS entries. This seems high. This means that if you make DNS changes those changes may not propagate throughout the internet for a long time.
Everyone that runs a web server or even a site needs to run a DNS check from time to time. For a long time I have been a happy user of a site DNSstuff.com. But couple of months ago they started charging for their main check called DNSReport.For few queries a month I’m not willing to subscribe for $80 a year, and I’m certainly not alone.
Finally I have done some research and tried to find alternatives. Here are the results with ratings, where 10/10 is what DNSReport gave us.
CheckDNS.net - 7/10 - SampleClear design, errors and warning are nicely visible. Quite fast too. Too bad it check for only basic stuff.
ZoneCheck - 6/10AJAXy. Only reports error and/or warning. Had a batch mode for multiple domains and desktop program which I don’t want to even try. DNS test should be available anywhere anytime.
intoDNS - 8/10 - SampleSimple, powerful, web2.0-ish. Results are almost identical to DNSReport, it’s just that the explanations are not that concise. For example, it says my SOA REFRESH is not ok, but I don’t get any recommendations on how to fix it.
Network Tools - 5/10Only stand alone tools, not DNSReport- like check. Trace and ping are nice though.
pingability - 7/10 - SampleSolid report, too bad it is terribly hard to read.
iptools.com - 4/10Similar to Network tools, it only has standalone tools, but no big all-round DNS test. Boring.
DomainTools - 2/10 - SampleToo simple. Only lists DNS entries.
Free DNS Report - 8/10 (scam?) - SampleThe report looks remarkably similar to that of the original, but the site looks terribly like a scam. I’m kind of scared to enter my domain name in there. If this is real test, please pimp it up a bit!
you get signal - not ratedDoesn’t really belong on the list, but it is a nice tool anyway. I use it for port forwarding tests and reverse IP domain check.
My pick is intoDNS. If I need a second opinion, I’ll go for CheckDNS.net or pingability. For port scanning and trace router I like you get signal the best.
Free DNS check online tool
Mozilla Labs » Blog Archive » Introducing Ubiquity
It Doesn’t Have to be This WayYou’re writing an email to invite a friend to meet at a local San Francisco restaurant that neither of you has been to. You’d like to include a map. Today, this involves the disjointed tasks of message composition on a web-mail service, mapping the address on a map site, searching for reviews on the restaurant on a search engine, and finally copying all links into the message being composed. This familiar sequence is an awful lot of clicking, typing, searching, copying, and pasting in order to do a very simple task. And you haven’t even really sent a map or useful reviews—only links to them.
This kind of clunky, time-consuming interaction is common on the Web. Mashups help in some cases but they are static, require Web development skills, and are largely site-centric rather than user-centric.
It’s even worse on mobile devices, where limited capability and fidelity makes this onerous or nearly impossible.
Most people do not have an easy way to manage the vast resources of the Web to simplify their task at hand. For the most part they are left trundling between web sites, performing common tasks resulting in frustration and wasted time.
Enter UbiquityToday we’re announcing the launch of Ubiquity, a Mozilla Labs experiment into connecting the Web with language in an attempt to find new user interfaces that could make it possible for everyone to do common Web tasks more quickly and easily.
The overall goals of Ubiquity are to explore how best to:
* Empower users to control the web browser with language-based instructions. (With search, users type what they want to find. With Ubiquity, they type what they want to do.)
* Enable on-demand, user-generated mashups with existing open Web APIs. (In other words, allowing everyone–not just Web developers–to remix the Web so it fits their needs, no matter what page they are on, or what they are doing.)
* Use Trust networks and social constructs to balance security with ease of extensibility.
* Extend the browser functionality easily.