<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">
<rss version="0.91">
	<channel>
		<language>en_GB</language>
		<title>Articles Tagged with &quot;Domains&quot;</title>
		<link>http://tobyinkster.co.uk/tag/domains/</link>
		<description></description>
		<item>
			<title>10/01/2008: NetSol Cybersquatting</title>
			<link>http://tobyinkster.co.uk/blog/2008/01/10/netsol-cybersquatting/</link>
			<description>&lt;p&gt;Over the last couple of days I&amp;#8217;ve read a few stories about &lt;a href=&quot;http://www.networksolutions.com/&quot;&gt;Network Solutions&lt;/a&gt; pulling a &lt;a href=&quot;http://en.wikipedia.org/wiki/Site_Finder&quot;&gt;Site Finder&lt;/a&gt; by stealing unregistered domain names on which people have run a &lt;a href=&quot;http://en.wikipedia.org/wiki/Whois&quot;&gt;whois&lt;/a&gt; query.&lt;/p&gt;

&lt;p&gt;They wait for people to whois query a domain (commonly done as a first step to registering a domain&amp;nbsp;&amp;#8212; to check that nobody already owns it), and if nobody owns it, they temporarily register it for five days (after which they&amp;#8217;d have to pay for it themselves!) and thus prevent anyone from registering the domain name using a competing registrar. &lt;a href=&quot;http://commandline.org.uk/more/squat-for-the-win-2008-01-09-03-36&quot;&gt;More details here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;According to &lt;span class=&quot;caps&quot;&gt;CNET, &lt;/span&gt;they&amp;#8217;ve &lt;a href=&quot;http://www.news.com/8301-10784_3-9847684-7.html?tag=nefd.blgs&quot;&gt;already started backpeddling&lt;/a&gt; on this.&lt;/p&gt;</description>
		</item>
		<item>
			<title>19/07/2007: PHP Domain Class</title>
			<link>http://tobyinkster.co.uk/blog/2007/07/19/php-domain-class/</link>
			<description>&lt;p&gt;On Usenet an often-asked question is how to programmatically determine the &amp;#8220;domain&amp;#8221; of a particular hostname. That is, excluding the components traditionally thought of as subdomains. As an example, &lt;tt&gt;groups.google.com&lt;/tt&gt; and &lt;tt&gt;www.google.com&lt;/tt&gt; both have a domain of &lt;tt&gt;google.com&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;Invariably, one answer comes back stating that you just need to chop off everything from the front, leaving only the last two components. But then someone will chime in pointing out that &lt;tt&gt;groups.google.co.uk&lt;/tt&gt; would be left as just &lt;tt&gt;co.uk&lt;/tt&gt; that way, when what is really wanted is &lt;tt&gt;google.co.uk&lt;/tt&gt;. And the eventual resolution of the argument will be &amp;#8220;it just can&amp;#8217;t be done&amp;#8221;.&lt;/p&gt;

&lt;p&gt;The problem is that there&amp;#8217;s technically no difference between a domain and a subdomain: it&amp;#8217;s simply a matter of convention. Fortunately, this issue is actually quite important to browser programmers, as it&amp;#8217;s a key issue in cookie security: browsers must allow subdomains within a domain to share cookie data, but not allow cookies&amp;#8230;&lt;/p&gt;</description>
		</item>
	</channel>
</rss>
