In Brief having a Public DNS has two advantages.

1. Faster Performance, Page loads
2. Better Security

Below are a few way a public DNS helps in more details courtesy Google

• Performance. Many DNS service providers are not sufficiently provisioned to be able to support high-volume input/output and caching, and adequately balance load among their servers. In addition to load-balancing user traffic to ensure shared caching, Google Public DNS implements “smart” caching to increase the speed of responses. Google Public DNS independently resolves domain names and keeps the resolutions in the cache until their time-to-live (TTL) expires, at which point they are automatically refreshed. The cycle of caching and refreshing is performed offline, asynchronously with user requests, so that responses are almost always available directly from cache. For more information, see the page on performance benefits.
• Security. DNS is vulnerable to various kinds of spoofing attacks that can “poison” a nameserver’s cache and route its users to malicious sites. The prevalence of DNS exploits means that providers have to frequently apply server updates and patches. In addition, open DNS resolvers are vulnerable to being used to launch denial-of-service (DoS) attacks on other systems. To defend against such attacks, Google has implemented several recommended solutions to help guarantee the authenticity of the responses it receives from other nameservers, and to ensure our servers are not used for launching DoS attacks. These include adding entropy to requests, rate-limiting client traffic, and more. For more information, see the page on security benefits.
• Correct results. Google Public DNS does its best to return the right answer to every query every time, in accordance with the DNS standards. Sometimes, in the case of a query for a mistyped or non-existent domain name, the right answer means no answer, or an error message stating the domain name could not be resolved. Google Public DNS never blocks, filters, or redirects users, unlike some open resolvers and ISPs.

Before we Begin on how to configure Google Public DNS Service I have listed out a few more alternatives below

List Of Free Public DNS Servers

Google

• 8.8.8.8
• 8.8.4.4

OpenDNS

• 208.67.222.222
• 208.67.220.220

ScrubIt

• 67.138.54.100
• 207.225.209.66

dnsadvantage

• 156.154.70.1
• 156.154.71.1

vnsc-pri.sys.gtei.net

• 4.2.2.1
• 4.2.2.2
• 4.2.2.3
• 4.2.2.4
• 4.2.2.5
• 4.2.2.6

Configuring your network settings to use Google Public DNS

When you use Google Public DNS, you are changing your DNS “switchboard” operator from your ISP to Google Public DNS.

In most cases, the IP addresses used by your ISP’s domain name servers are automatically set by your ISP via the Dynamic Host Configuration Protocol (DHCP). To use Google Public DNS, you need to explicitly change the DNS settings in your operating system or device to use the Google Public DNS IP addresses. The procedure for changing your DNS settings varies according to operating system and version (Windows, Mac or Linux) or the device (computer, phone, or router). We give general procedures here that might not apply for your OS or device; please consult your vendor documentation for authoritative information.

Note: We recommend that only users who are proficient with configuring operating system settings make these changes.

Important: Before you start

Before you change your DNS settings to use Google Public DNS, be sure to write down the current server addresses or settings on a piece of paper. It is very important that you keep these numbers for backup purposes, in case you need to revert to them at any time.

After changing your settings, if you encounter a problem and cannot connect to the Internet, call Google’s support numbers for troubleshooting instructions.

you can download this tutorial and print it, in the event that you encounter a problem and need to refer to these instructions.

Google Public DNS IP addresses

The Google Public DNS IP addresses are as follows:

• 8.8.8.8
• 8.8.4.4

You can use either number as your primary or secondary DNS server. You can specify both numbers, but do not specify one number as both primary and secondary.

Changing your DNS servers settings

Many systems allow you to specify multiple DNS servers, to be contacted in a priority order. In the following instructions, we provide steps to specify only the Google Public DNS servers as the primary and secondary servers, to ensure that your setup will correctly use Google Public DNS in all cases.

Note: Depending on your network setup, you may need administrator/root privileges to change these settings.

Microsoft Windows

DNS settings are specified in the TCP/IP Properties window for the selected network connection.

Example: Changing DNS server settings on Microsoft Windows Vista

1. Go the Control Panel.
2. Click Network and Internet, then Network and Sharing Center, then Manage network connections.
3. Select the connection for which you want to configure Google Public DNS. For example:
   • To change the settings for an Ethernet connection, right-click Local Area Connection, and click Properties.
   • To change the settings for a wireless connection, right-click Wireless Network Connection, and click Properties.

   If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

4. Select the Networking tab. Under This connection uses the following items, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
5. Click Advanced and select the DNS tab. If there are any DNS server IP addresses listed there, write them down for future reference, and remove them from this window.
6. Click OK.
7. Select Use the following DNS server addresses. If there are any IP addresses listed in the Preferred DNS server or Alternate DNS server, write them down for future reference.
8. Replace those addresses with the IP addresses of the Google DNS servers: 8.8.8.8 and 8.8.4.4.
9. Restart the connection you selected in step 3.
10. Test that your setup is working correctly; see Testing your new settings below.
11. Repeat the procedure for additional network connections you want to change.

Mac OS X

DNS settings are specified in the Network window.

Example: Changing DNS server settings on Mac OS 10.5

1. From the Apple menu, click System Preferences, then click Network. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
2. Select the connection for which you want to configure Google Public DNS. For example:
   • To change the settings for an Ethernet connection, select Built-In Ethernet, and click Advanced.
   • To change the settings for a wireless connection, select Airport, and click Advanced.
3. Select the DNS tab.
4. Click + to replace any listed addresses with, or add, the Google IP addresses at the top of the list: 8.8.8.8 and 8.8.4.4.
5. Click Apply and OK.
6. Test that your setup is working correctly; see Testing your new settings below.
7. Repeat the procedure for additional network connections you want to change.

Linux

In most modern Linux distributions, DNS settings are configured through Network Manager.

Example: Changing DNS server settings on Ubuntu

1. In the System menu, click Preferences, then click Network Connections.
2. Select the connection for which you want to configure Google Public DNS. For example:
   • To change the settings for an Ethernet connection, select the Wired tab, then select your network interface in the list. It is usually called eth0.
   • To change the settings for a wireless connection, select the Wireless tab, then select the appropriate wireless network.
3. Click Edit, and in the window that appears, select the IPv4 Settings tab.
4. If the selected method is Automatic (DHCP), open the dropdown and select Automatic (DHCP) addresses only instead. If the method is set to something else, do not change it.
5. In the DNS servers field, enter the Google Public DNS IP addresses, separated by a space: 8.8.8.8  8.8.4.4
6. Click Apply to save the change. If you are prompted for a password or confirmation, type the password or provide confirmation.
7. Test that your setup is working correctly; see Testing your new settings below.
8. Repeat the procedure for additional network connections you want to change.

If your distribution doesn’t use Network Manager, your DNS settings are specified in /etc/resolv.conf.

Example: Changing DNS server settings on a Debian server

1. Edit /etc/resolv.conf:

   sudo vi /etc/resolv.conf

2. If any nameserver lines appear, write down the IP addresses for future reference.
3. Replace the nameserver lines with, or add, the following lines:

   nameserver 8.8.8.8
   nameserver 8.8.4.4

4. Save and exit.
5. Restart any Internet clients you are using.
6. Test that your setup is working correctly; see Testing your new settings below.

Additionally, if you are using DHCP client software that overwrites the settings in /etc/resolv.conf, you will need to set up the client accordingly by editing the client’s configuration file.

Example: Configuring DHCP client sofware on a Debian server

1. Back up /etc/resolv.conf:

   sudo cp /etc/resolv.conf /etc/resolv.conf.auto

2. Edit /etc/dhcp3/dhclient.conf:

   sudo vi /etc/dhcp3/dhclient.conf

3. If there is a line containing domain-name-servers, write down the IP addresses for future reference.
4. Replace that line with, or add, the following line:

   prepend domain-name-servers 8.8.8.8, 8.8.4.4;

5. Save and exit.
6. Restart any Internet clients you are using.
7. Test that your setup is working correctly; see Testing your new settings below.

Routers

Every router uses a different user interface for configuring DNS server settings; we provide only a generic procedure below. For more information, please consult your router documentation.

Note: Some ISPs hard-code their DNS servers into the equipment they provide; if you are using such a device, you will not be able to configure it to use Google Public DNS. Instead, you can configure each of the computers connected to the router, as described above.

To change your settings on a router:

1. In your browser, enter the IP address to access the router’s administration console.
2. When prompted, enter the password to access network settings.
3. Find the screen in which DNS server settings are specified.
4. If there are IP addresses specified in the fields for the primary and seconday DNS servers, write them down for future reference.
5. Replace those addresses with Google IP addresses: 8.8.8.8 and 8.8.4.4.
6. Save and exit.
7. Restart your browser.
8. Test that your setup is working correctly; see Testing your new settings below.

Mobile or other devices

DNS servers are typically specified under advanced wi-fi settings. However, as every mobile device uses a different user interface for configuring DNS server settings, we provide only a generic procedure below. For more information, please consult your mobile provider’s documentation.

To change your settings on a mobile device:

1. Go to the screen in which wi-fi settings are specified.
2. Find the screen in which DNS server settings are specified.
3. If there are IP addresses specified in the fields for the primary and seconday DNS servers, write them down for future reference.
4. Replace those addresses with Google IP addresses: 8.8.8.8 and 8.8.4.4.
5. Save and exit.
6. Test that your setup is working correctly; see Testing your new settings below.

Testing your new settings

To test that the Google DNS resolver is working:

1. From your browser, type in a hostname, such as http://www.google.com. If it resolves correctly, bookmark the page, and try accessing the page from the bookmark. If both of these tests work, everything is working correctly. If not, go to step 2.
2. From your browser, type in a fixed IP address. You can use http://18.62.1.6/ (which points to the website http://eecs.mit.edu/) as the URL*. If this works correctly, bookmark the page, and try accessing the page from the bookmark. If these tests work (but step 1 fails), then there is a problem with your DNS configuration; check the steps above to make sure you have configured everything correctly. If these tests do not work, go to step 3.
3. Roll back the DNS changes you made and run the tests again. If the tests still do not work, then there is a problem with your network settings; contact your ISP or network administrator for assistance.

* Google thanks MIT for granting permission to use this URL for the purposes of testing web connectivity.

Switching back to your old DNS settings

If you had not previously configured any customized DNS servers, to switch back to your old settings, in the window in which you specified the Google IP addresses, select the option to enable obtaining DNS server addresses automatically, and/or delete the Google IP addresses. This will revert your settings to using your ISP’s default servers.

If you need to manually specify any addresses, use the procedures above to specify the old IP addresses.

If necessary, restart your system.

The Guide above has been provided by Google you can read the original tutorial at Google Code

Related posts:

1. Google Updater Service Uninstall, Disable Or Configure The Complete Guide
2. Unlimited Free International Calls & SMS After Activating Google Voice Outside US
3. Unblock Blocked Websites like Myspace, Bebo and Orkut
4. Uninstall Google Gears From Mac OS X, Windows, Linux
5. Facebook Chat, Google Gtalk Intergration Coming Soon

© Arpit Jacob for Clazh, 2009. | Permalink | 5 comments | Add to del.icio.us
Catergories: Google, How To Tags: Browser, DNS, Guide, How To, Performance, Tuneup

Internet Explorer 9 Whats new?

Increased JavaScript Performance

The latest builds of Internet Explorer 9 shows that the performance is comparable to that of FireFox 3.6 and Chrome 4 and the latest Web Kit Nightly build. If true this is a huge improvement.

Internet Explorer 9 JavaScript Performance

Standards Support CSS 3.0 and HTML 5

What does that mean? In plain english it means support for rounded corners, text shadows, Box shadows, video support etc without the need for using images or scripts. Thought the latest ACID 3 test for Internet Explorer 9 doesn’t seem to be that great.

Acid 3

Rounded Corners

CSS Selectors

Uses Graphics hardware acceleration for rendering

We’re changing IE to use the DirectX family of Windows APIs to enable many advances for web developers. The starting point is moving all graphics and text rendering from the CPU to the graphics card using Direct2D and DirectWrite. Graphics hardware acceleration means that rich, graphically intensive sites can render faster while using less CPU. Now, web developers can take advantage of the hardware ecosystem’s advances in graphics while they continue to author sites with the same interoperable standards patterns they’re used to.

In addition to better performance, this technology shift also increases font quality and readability with sub-pixel positioning

Rendering of font normally

96 point Gabriola on a Lenovo X61 ThinkPad at 100% Zoom using GDI (note jaggies)

Rendering of font using Graphic card hardware

96 point Gabriola on a Lenovo X61 ThinkPad at 100% Zoom: Direct2D (without jaggies)

SilverLight 4 Whats new?

Empowering richer, more interactive experiences

Silverlight is already in use as a comprehensive platform for building rich experiences both for application and pure media scenarios including HD quality, interactive video through Smooth Streaming. Silverlight 4 introduces additional capabilities to enable creation of ever more rich, appealing high-performance interactive experiences and innovative media experiences:

• Fluid interface enhancements advance application usability through animation effects.
• Webcam and microphone to allow sharing of video and audio for instance for chat or customer service applications.
• Audio and video local recording capabilities capture RAW video without requiring server interaction, enabling a wide range of end-user interaction and communication scenarios for example video conferencing.
• Bring data in to your application with features such as copy and paste or drag and drop.
• Long lists can now be scrolled effortlessly with the mouse wheel.
• Support conventional desktop interaction models through new features such as right-click context menu.
• Support for Google’s Chrome browser.
• Performance optimizations mean Silverlight 4 applications start quicker and run 200% faster than the equivalent Silverlight 3 application.
• Deep Zoom enhancements include hardware acceleration to support larger datasets and faster animation.
• Multi-touch support enables a range of gestures and touch interactions to be integrated into user experiences.
• Multicast networking, enabling Enterprises to lower the cost of streaming broadcast events such as company meetings and training, interoperating seamlessly with existing Windows Media Server streaming infrastructure.
• Content protection for H.264 media through Silverlight DRM powered by PlayReady.
• Output protection for audio/video streams allowing content owners or distributors to ensure protected content is only viewed through a secure video connection.

For Sandboxed applications

• Place HTML within your application enabling much tighter integration with content from web servers such as email, help and reports.
• Provide support for ‘toast’ notification windows, allowing applications to communicate status or change information while the user is working on another application through a popup window on the taskbar.
• Offline DRM, extending the existing Silverlight DRM powered by PlayReady technology to work offline. Protected content can be delivered with an embedded license so that users can go offline immediately and start enjoying their content.
• Control over aspects of UI include window settings such as start position, size and chrome.

For Trusted applications

• Read and write files to the user’s MyDocuments, MyMusic, MyPictures and MyVideos folder (or equivalent for non-windows platforms) for example storage of media files and taking local copies of reports.
• Run other desktop programs such as Office, for example requesting Outlook to send an email, send a report to Word or data to Excel.
• COM automation enables access to devices and other system capabilities by calling into application components; for instance to access a USB security card reader.
• A new user interface for requesting application privileges access outside the standard Silverlight sandbox.
• Group policy objects allow organizations to tailor which applications may have elevated trust.
• Full keyboard support in fullscreen mode richer kiosk and media applications.
• Enhancements to networking allow cross-domain access without a security policy file.

Related posts:

1. Download Internet Explorer 8 Beta, New Features In IE8
2. The SilverLight Poster and more on Silverlight and Microsoft
3. Google Chrome OS All About it – Breaking News
4. Prism and XUL Could Have Been A Silverlight And Adobe AIR Killer
5. Microsoft We Screwed Up Windows Mobile, iPhone Competitor Silverlight Mobile 2010

© Arpit Jacob for Clazh, 2009. | Permalink | One comment | Add to del.icio.us
Catergories: Microsoft, Windows Tags: Browser, Internet Explorer, Silverlight