I pushed 30 of my projects to GitHub - good coders code, great r. Hey everyone, I just pushed 30 of my projects to GitHub. I realized that all the projects were scattered across my blog and there was no central repository. So I took time to organize them, write documentation, and uploaded them to GitHub. I did all of these projects for fun and to learn better programming.
You can't become a great programmer if you don't program a lot. The more you program, the more language idioms and constructs you'll learn. You'll learn common patterns that occur frequently in programming and it will greatly improve your problem solving skills. These were all relatively small projects and I think I am ready to move to the next level. If you find any of my projects interesting, clone and start hacking. Here they all are. 1. Busy beaver is a computer science problem to finding the smallest Turing Machine that outputs the most data and eventually halts. 2. Current Feedburner statistics graphs do not look nice. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. Blog » Some thoughts on Google DNS. Google launched a DNS service today, almost exactly four years after I started OpenDNS. This comes as no surprise as it was only a matter of time before one of the Internet giants realized the strategic importance of DNS.
I’ve received a lot of questions from bloggers, journalists, friends and most importantly, our users. And so I want to share my thoughts on what this means for the recursive DNS space and what it means for OpenDNS. First, it’s not the same as OpenDNS. When you use Google DNS, you are getting the experience they prescribe. When you use OpenDNS, you get the Dashboard controls to manage your experience the way you want for you, your family or your organization. People use OpenDNS because we are pioneers and innovators in the DNS space, offering the most secure recursive DNS service around. Third, Google claims that this service is better because it has no ads or redirection. So how will this impact us? Performance Benefits. Introduction: causes and mitigations of DNS latency As web pages become more complex, referencing resources from numerous domains, DNS lookups can become a significant bottleneck in the browsing experience.
Whenever a client needs to query a DNS resolver over the network, the latency introduced can be significant, depending on the proximity and number of nameservers the resolver has to query (more than 2 is rare, but it can happen). As an example, the following screen shot shows the timings reported by the Page Speed web performance measurement tool. Each bar represents a resource referenced from the page; the black segments indicate DNS lookups. In this page, 13 lookups are made in the first 11 seconds in which the page is loaded.
There are two components to DNS latency: Latency between the client (user) and DNS resolving server. We believe that the cache miss factor is the most dominant cause of DNS latency, and discuss it further below. Cache misses Internet size and growth. Mitigations. DNStunnel.de - free DNS tunneling service. Ubuntu Blog & Local DNS Cache for Faster Browsing. Posted by Carthik in administration, guides, packages, ubuntu. Trackback A DNS server resolves domain names into IP addresses. So when you request “google.com” for example, the DNS server finds out the address for the domain, and sends your request the right way. You can run a DNS cache on your computer. This will speed up the process of looking up domain names when browsing. The following instructions are for someone with a cable (broadband) internet connection, where the computer gets it’s local IP address using DHCP from the router in your house/office: The package we will be using for caching nameserver lookups is called dnsmasq.
No uncomment the following line (that is edit the line to NOT have a “#” in the beginning) in the file /etc/dnsmasq.conf:listen-address=127.0.0.1 Now open the file /etc/resolv.conf in your text editor. The 127.0.0.1 is missing right now since you haven’t renewed your lease after you edited the /etc/dhcp3/dhclient.conf file. Okay. Like this: Like Loading... How to protect your domain names from hija. SPECIAL REPORT: How to protect your domain name from hijackers, porn pirates, and your registrar. Is your domain really safe? If you are not prepared, there are a number of common mistakes which can result in the permanent loss of your domain. Owners of multiple domain names are particularly at risk. This article explains the most common ways that domains are lost and gives specific advice on how to safeguard your names. As a domain owner, you should be aware of and protect yourself against the following three scenarios.. 1. Inadvertent domain expiration: The owner does not renew the name in time and it is snatched up by a domain speculator.
Most registrars no longer send out renewal notices via postal mail. Once deleted, domains are commonly snatched up within seconds by speculators running automated programs. 2. Once the hijacker has control of the name, they will usually assume ownership of the domain and start redirecting it to their own web sites. 3. How to protect yourself... 1. 2. Buy Domains, Domain Registration and Web H.