<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>KutuKupret</title>
	
	<link>http://www.kutukupret.com</link>
	<description>My Colourful Website ;)</description>
	<lastBuildDate>Tue, 31 Aug 2010 03:01:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/Kutukupret" /><feedburner:info uri="kutukupret" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Nginx enabling TLS SNI support on centos 5</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/Ay2YictfZ_Y/</link>
		<comments>http://www.kutukupret.com/2010/08/30/nginx-enabling-tls-sni-support-on-centos-5/#comments</comments>
		<pubDate>Mon, 30 Aug 2010 06:22:37 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[http]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[rpm]]></category>
		<category><![CDATA[SNI]]></category>
		<category><![CDATA[tls]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=954</guid>
		<description>By default centos 5.x has openssl-0.9.8e which is not have tls extention for  sni support. this is workaround on how to get nginx 0.8.48 rpm with TLS SNI enabled Step 1: download openssl source, example  openssl-0.9.8l. extract it in /usr/src $ cd /usr/src $ wget http://www.openssl.org/source/openssl-0.9.8l.tar.gz $ tar xvzf openssl-0.9.8l.tar.gz Step 2: Download nginx rpm [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/3ScGClnKAnhsjMzM-Fq8P43Ki5A/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3ScGClnKAnhsjMzM-Fq8P43Ki5A/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/3ScGClnKAnhsjMzM-Fq8P43Ki5A/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3ScGClnKAnhsjMzM-Fq8P43Ki5A/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/Ay2YictfZ_Y" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/30/nginx-enabling-tls-sni-support-on-centos-5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/30/nginx-enabling-tls-sni-support-on-centos-5/</feedburner:origLink></item>
		<item>
		<title>test the round robin DNS features of the resolver functions</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/I4_5ST0RfZ4/</link>
		<comments>http://www.kutukupret.com/2010/08/24/test-the-round-robin-dns-features-of-the-resolver-functions/#comments</comments>
		<pubDate>Tue, 24 Aug 2010 06:58:03 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[c]]></category>
		<category><![CDATA[dns]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[gcc]]></category>
		<category><![CDATA[getaddrinfo()]]></category>
		<category><![CDATA[gethostbyname()]]></category>
		<category><![CDATA[roundrobin]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=946</guid>
		<description>Date: 3 Nov 2005 Author: Daniel Stenberg License: freely available to do whatever you want with. roundrobin.c &amp;#8211; test the round robin DNS features of the resolver functions Note: this test script is written to be compiled and run on Linux. It is not as portable as it could be, but that is just to [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/yEUNKlvhPNMTgxZD13V3Q_aWDGs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yEUNKlvhPNMTgxZD13V3Q_aWDGs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/yEUNKlvhPNMTgxZD13V3Q_aWDGs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yEUNKlvhPNMTgxZD13V3Q_aWDGs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/I4_5ST0RfZ4" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/24/test-the-round-robin-dns-features-of-the-resolver-functions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/24/test-the-round-robin-dns-features-of-the-resolver-functions/</feedburner:origLink></item>
		<item>
		<title>Nginx, fastcgi, ‘Hello World’ in C</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/hYrOEzeNVSM/</link>
		<comments>http://www.kutukupret.com/2010/08/20/nginx-fastcgi-hello-world-in-c/#comments</comments>
		<pubDate>Fri, 20 Aug 2010 02:27:29 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[c]]></category>
		<category><![CDATA[cgi]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[fastcgi]]></category>
		<category><![CDATA[Hello World]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[spawn-cgi]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=939</guid>
		<description>Here is a simple example of a hello world program for FastCGI written in C. Before you can compile this, you will need to install the FastCGI devkit. At the time of writing the latest version is available from www.fastcgi.com extract, compile and install fcgi-current.tar.gz $ tar xvzf fcgi-current.tar.gz $ cd  fcgi-2.x.x/ $ ./configure $ make [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/fNm8b7Jplc-WEgDe4erpnT7mq-E/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/fNm8b7Jplc-WEgDe4erpnT7mq-E/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/fNm8b7Jplc-WEgDe4erpnT7mq-E/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/fNm8b7Jplc-WEgDe4erpnT7mq-E/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/hYrOEzeNVSM" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/20/nginx-fastcgi-hello-world-in-c/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/20/nginx-fastcgi-hello-world-in-c/</feedburner:origLink></item>
		<item>
		<title>Change Nginx Version Header</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/EhZ8Y3rscbM/</link>
		<comments>http://www.kutukupret.com/2010/08/19/change-nginx-version-header/#comments</comments>
		<pubDate>Thu, 19 Aug 2010 02:19:14 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[http]]></category>
		<category><![CDATA[header]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[version]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=935</guid>
		<description>Edit nginx.h $ vi src/core/nginx.h find lines: #define NGINX_VERSION &amp;#34;0.7.64&amp;#34; #define NGINX_VER &amp;#34;nginx/&amp;#34; NGINX_VERSION Change them as follows: #define NGINX_VERSION &amp;#34;0.0.7&amp;#34; #define NGINX_VER &amp;#34;kutukupret/&amp;#34; NGINX_VERSION Save and close the file. Now, you can compile the server. Add the following in nginx.conf to turn off nginx version number displayed on all auto generated error pages: server_tokens [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/1ScEe7LQ6WB-AEiWPdMTbY7kbEQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1ScEe7LQ6WB-AEiWPdMTbY7kbEQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/1ScEe7LQ6WB-AEiWPdMTbY7kbEQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1ScEe7LQ6WB-AEiWPdMTbY7kbEQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/EhZ8Y3rscbM" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/19/change-nginx-version-header/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/19/change-nginx-version-header/</feedburner:origLink></item>
		<item>
		<title>Nginx Limit Available Methods</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/gl5WHRlxrFQ/</link>
		<comments>http://www.kutukupret.com/2010/08/19/nginx-limit-available-methods/#comments</comments>
		<pubDate>Thu, 19 Aug 2010 02:01:38 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[http]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[GET]]></category>
		<category><![CDATA[HEAD]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[OPTIONS]]></category>
		<category><![CDATA[POST]]></category>
		<category><![CDATA[RFC2616]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=934</guid>
		<description>GET and POST are the most common methods on the Internet. Web server methods are defined in RFC 2616. If a web server does not require the implementation of all available methods, they should be disabled. The following will filter and only allow GET, HEAD and POST methods: ## Only allow these request methods ## [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/w6_Ctpwz_DtRUlF9FH0dRygVC4U/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/w6_Ctpwz_DtRUlF9FH0dRygVC4U/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/w6_Ctpwz_DtRUlF9FH0dRygVC4U/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/w6_Ctpwz_DtRUlF9FH0dRygVC4U/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/gl5WHRlxrFQ" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/19/nginx-limit-available-methods/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/19/nginx-limit-available-methods/</feedburner:origLink></item>
		<item>
		<title>Nginx SSL/HTTPS</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/pG7cAAGyNUw/</link>
		<comments>http://www.kutukupret.com/2010/08/19/nginx-sslhttps/#comments</comments>
		<pubDate>Thu, 19 Aug 2010 01:15:37 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[http]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=932</guid>
		<description>HTTP is a plain text protocol and it is open to passive monitoring. You should use SSL to to encrypt your content for users. Create an SSL Certificate Type the following commands: $ cd /usr/local/nginx/conf $ openssl genrsa -des3 -out server.key 1024 $ openssl req -new -key server.key -out server.csr $ cp server.key server.key.org $ [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/tCXhZ6KYTQZn6cHLCjj7zR_x9xU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tCXhZ6KYTQZn6cHLCjj7zR_x9xU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/tCXhZ6KYTQZn6cHLCjj7zR_x9xU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tCXhZ6KYTQZn6cHLCjj7zR_x9xU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/pG7cAAGyNUw" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/19/nginx-sslhttps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/19/nginx-sslhttps/</feedburner:origLink></item>
		<item>
		<title>Nginx Image Hotlink Prevention</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/9RQaPM8BnPY/</link>
		<comments>http://www.kutukupret.com/2010/08/18/nginx-image-hotlink-prevention/#comments</comments>
		<pubDate>Wed, 18 Aug 2010 03:37:23 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[http]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[hijack]]></category>
		<category><![CDATA[hotlink]]></category>
		<category><![CDATA[image]]></category>
		<category><![CDATA[nginx]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=931</guid>
		<description>how to prevent image hotlinking with nginx? this will return 403 error when someone trying to use image directly from oursite. location ~* (\.jpg&amp;#124;\.png&amp;#124;\.gif&amp;#124;\.jpeg&amp;#124;\.png)$ { valid_referers none blocked www.example.com example.com; if ($invalid_referer) { return 403; } } or we can change every images which hotlinked with our custom banner. valid_referers none blocked www.example.com example.com; if [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/mwrJC5AJ0lDMUENgTfR6ecxrG60/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mwrJC5AJ0lDMUENgTfR6ecxrG60/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/mwrJC5AJ0lDMUENgTfR6ecxrG60/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mwrJC5AJ0lDMUENgTfR6ecxrG60/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/9RQaPM8BnPY" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/18/nginx-image-hotlink-prevention/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/18/nginx-image-hotlink-prevention/</feedburner:origLink></item>
		<item>
		<title>Extract ipv6 prefix in python</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/dV9Zc91TcZw/</link>
		<comments>http://www.kutukupret.com/2010/08/18/extract-ipv6-prefix-in-python/#comments</comments>
		<pubDate>Wed, 18 Aug 2010 01:36:48 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[ipv6]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[ipaddr-py]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=930</guid>
		<description>See http://code.google.com/p/ipaddr-py/ With this, we can do py&amp;#62; p=ipaddr.IPv6(&amp;#34;2001:888:2000:d::a2&amp;#34;) py&amp;#62; p.SetPrefix(64) py&amp;#62; p IPv6('2001:888:2000:d::a2/64') py&amp;#62; p.network_ext '2001:888:2000:d::'
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/WrnDI1CwVcgIHPe-5m__4KQAzD4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/WrnDI1CwVcgIHPe-5m__4KQAzD4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/WrnDI1CwVcgIHPe-5m__4KQAzD4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/WrnDI1CwVcgIHPe-5m__4KQAzD4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/dV9Zc91TcZw" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/18/extract-ipv6-prefix-in-python/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/18/extract-ipv6-prefix-in-python/</feedburner:origLink></item>
		<item>
		<title>Nginx – Customizing 404 page</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/LtV6__vmb9I/</link>
		<comments>http://www.kutukupret.com/2010/08/16/nginx-customizing-404-page/#comments</comments>
		<pubDate>Mon, 16 Aug 2010 03:24:49 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[http]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[404]]></category>
		<category><![CDATA[404 page]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[error code]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[nginx]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=925</guid>
		<description>You can setup a custom error page for every location block in your nginx.conf, or a global error page for the site as a whole. To redirect to a simple 404 not found page for a specific location: location /my_blog { error_page 404 = /article_not_found.html; } A site wide 404 page: server { listen 80; [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/s8aJq1iPHp1SA2AFrIIJ0iRuMs0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/s8aJq1iPHp1SA2AFrIIJ0iRuMs0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/s8aJq1iPHp1SA2AFrIIJ0iRuMs0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/s8aJq1iPHp1SA2AFrIIJ0iRuMs0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/LtV6__vmb9I" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/16/nginx-customizing-404-page/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/16/nginx-customizing-404-page/</feedburner:origLink></item>
		<item>
		<title>Using IPv6 with Custom and Secondary DNS</title>
		<link>http://feedproxy.google.com/~r/Kutukupret/~3/NRDJkX5RQ4w/</link>
		<comments>http://www.kutukupret.com/2010/08/06/using-ipv6-with-custom-and-secondary-dns/#comments</comments>
		<pubDate>Fri, 06 Aug 2010 13:16:35 +0000</pubDate>
		<dc:creator>leenoux</dc:creator>
				<category><![CDATA[dns]]></category>
		<category><![CDATA[ipv6]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[dyndns]]></category>

		<guid isPermaLink="false">http://www.kutukupret.com/?p=871</guid>
		<description>source: http://www.dyndns.com/support/kb/ipv6_with_custom_secdns.html As part of Dyn Inc.&amp;#8217;s IPv6 implementation plan, DynDNS.com has recently made a new IPv6 nameserver available for Custom DNS and Secondary DNS customers. Whether you&amp;#8217;re looking to get a jump on the transition to IPv6 or you&amp;#8217;re simply curious, we&amp;#8217;ve created this short tutorial to help you make use of the new nameserver. [...]
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/r2SCl6mEsTfY9H95XZnxK3aa7dM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/r2SCl6mEsTfY9H95XZnxK3aa7dM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/r2SCl6mEsTfY9H95XZnxK3aa7dM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/r2SCl6mEsTfY9H95XZnxK3aa7dM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Kutukupret/~4/NRDJkX5RQ4w" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.kutukupret.com/2010/08/06/using-ipv6-with-custom-and-secondary-dns/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.kutukupret.com/2010/08/06/using-ipv6-with-custom-and-secondary-dns/</feedburner:origLink></item>
	</channel>
</rss>
