<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>easyDNS Blog - Tips and Tricks</title>
    <link>http://blog.easydns.org/</link>
    <description>Happenings and observations from easyDNS</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.2.1 - http://www.s9y.org/</generator>
    <pubDate>Thu, 06 Nov 2008 18:11:31 GMT</pubDate>

    <image>
        <url>http://blog.easydns.org/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: easyDNS Blog - Tips and Tricks - Happenings and observations from easyDNS</title>
        <link>http://blog.easydns.org/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>MobileMe and easyDNS...</title>
    <link>http://blog.easydns.org/archives/243-MobileMe-and-easyDNS....html</link>
            <category>Tips and Tricks</category>
    
    <comments>http://blog.easydns.org/archives/243-MobileMe-and-easyDNS....html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=243</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=243</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    A number of customers have been registering domains to point to their new websites published via iWeb on their MobileMe accounts. Unfortunately, while MobileMe instructs how to point &quot;www.yourdomain.com&quot; to their services, they don&#039;t have a way to easily point just &quot;yourdomain.com&quot; to their services. This is especially important as not everyone on the internet will type &quot;www&quot; before a domain name when looking for a website (such as &quot;www.google.com&quot; versus &quot;google.com&quot;).&lt;br /&gt;
&lt;br /&gt;
Realising this is an issue for some of our customers who have DNS-Only services, we have implemented a work around. Simply follow the instructions on MobileMe to have your &quot;www.yourdomain.com&quot; CNAME point to &quot;web.me.com&quot;. These are correct, and are very important. However, one last step is to leave your &quot;yourdomain.com&quot; record in the &quot;hosts&quot; block pointing to the word &quot;PENDING&quot;. It should look something like this:&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;A record (host):&lt;/strong&gt;  yourdomain.com&lt;br /&gt;
&lt;strong&gt;Has IP:&lt;/strong&gt;  PENDING&lt;br /&gt;
&lt;br /&gt;
...with your CNAME looking like this:&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;C name (alias):&lt;/strong&gt;  www.yourdomain.com&lt;br /&gt;
&lt;strong&gt;Points to A record (host):&lt;/strong&gt;  web.me.com&lt;br /&gt;
&lt;br /&gt;
Once entered, click &quot;next&quot; to submit your changes, and &quot;next&quot; again after you have confirmed all looks well. These updates may take a few hours to propagate across the internet before you can see them.&lt;br /&gt;
&lt;br /&gt;
If you have any questions at all, please contact our Support Dept., and we would be happy to assist you. 
    </content:encoded>

    <pubDate>Thu, 06 Nov 2008 13:03:02 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/243-guid.html</guid>
    
</item>
<item>
    <title>How to explain &quot;URLs&quot; so anybody can understand them</title>
    <link>http://blog.easydns.org/archives/236-How-to-explain-URLs-so-anybody-can-understand-them.html</link>
            <category>Tips and Tricks</category>
    
    <comments>http://blog.easydns.org/archives/236-How-to-explain-URLs-so-anybody-can-understand-them.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=236</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=236</wfw:commentRss>
    

    <author>nospam@example.com (Mark Jeftovic)</author>
    <content:encoded>
    One of our tech support guys just had a conversation with somebody who wanted &quot;to register the URL http://example.com/something.html&quot;, where example.com was already registered, the person couldn&#039;t understand why he couldn&#039;t have that URL with &quot;something.html&quot; after it.&lt;br /&gt;
&lt;br /&gt;
We&#039;ve heard variations of this one a lot. Like somebody who knows &quot;xyz.zz&quot; is taken &quot;but can I register &quot;www.xyz.zz?&quot;, no, you can&#039;t.&lt;br /&gt;
&lt;br /&gt;
The easiest way to explain a URL such as this one:&lt;br /&gt;
&lt;br /&gt;
&lt;font size=+1&gt;http://www.example.com/something.html&lt;/font&gt;&lt;br /&gt;
&lt;br /&gt;
Is to think of it as HOW, then WHERE and finally WHAT:&lt;br /&gt;
&lt;br /&gt;
&lt;table cellspacing=5 cellpadding=5&gt;&lt;br /&gt;
&lt;tr&gt;&lt;br /&gt;
&lt;td valign=top&gt;&lt;b&gt;http://&lt;/b&gt;&lt;/td&gt;&lt;td valign=top align=left nowrap&gt;&amp;laquo; how?&lt;/td&gt;&lt;td&gt;The method we are going to use to retrieve or &quot;get to&quot; the document described by the URL. Common ones are &quot;http&quot; (Hyper-Text Transfer Protocol), you may also see &quot;ftp://&quot; or &quot;mailto:&quot;&lt;/td&gt;&lt;/tr&gt;&lt;br /&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;br /&gt;
&lt;b&gt;www.example.com&lt;/b&gt;&lt;/td&gt;&lt;td valign=top align=left nowrap&gt;&amp;laquo; where?&lt;/td&gt;&lt;td&gt;This is the hostname of the server, somewhere on the internet, which is holding the document we actually want&lt;/td&gt;&lt;/tr&gt;&lt;br /&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;br /&gt;
&lt;b&gt;/something.html&lt;/b&gt;&lt;/td&gt;&lt;td valign=top align=left nowrap&gt;&amp;laquo; what?&lt;/td&gt;&lt;td&gt;Finally, after we know what server we are looking for and how we&#039;re going to retrieve the document from it, we now specify exactly &lt;i&gt;which document&lt;/i&gt; we want off of the remote server.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;br /&gt;
&lt;br /&gt;
Understand those three components and you basically have URLs down cold. &lt;br /&gt;
&lt;br /&gt;
Your web browser (firefox, safari, IE, Opera) is all about &quot;how&quot;, what protocols to use to pull all these documents over the web to your desktop.&lt;br /&gt;
&lt;br /&gt;
The web host is the &quot;what&quot; machine. It sits on a server and serves document after document to remote web browsers who send it requests.&lt;br /&gt;
&lt;br /&gt;
Something has to bridge the browser to the web host/server and that&#039;s the &quot;where&quot;, that&#039;s where DNS and domains come in, and that&#039;s primarily what we do here at easyDNS. We tell web browsers (and other client applications) the &quot;where&quot; aspect of retrieving and transmitting documents (the &quot;whats&quot;) across the internet. We do this via &quot;DNS lookups&quot; ...about a quarter billion times a day. 
    </content:encoded>

    <pubDate>Tue, 28 Oct 2008 09:47:14 -0400</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/236-guid.html</guid>
    
</item>
<item>
    <title>Running an affiliate program? Don't pay for sales you already had in the bag</title>
    <link>http://blog.easydns.org/archives/227-Running-an-affiliate-program-Dont-pay-for-sales-you-already-had-in-the-bag.html</link>
            <category>Tips and Tricks</category>
    
    <comments>http://blog.easydns.org/archives/227-Running-an-affiliate-program-Dont-pay-for-sales-you-already-had-in-the-bag.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=227</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=227</wfw:commentRss>
    

    <author>nospam@example.com (Mark Jeftovic)</author>
    <content:encoded>
    People have tried this on us so many times I figure it must still work in many cases so after the last one I decided to post a brief note about this. &lt;br /&gt;
&lt;br /&gt;
We run an affiliate program via Commission Junction, it pays $20 per new customer acquisition. We also come up first in all major search engines for our own name: &quot;easydns&quot;, &quot;easydns.com&quot;, &quot;www.easydns.com&quot;, and &quot;easyDNS Technologies Inc&quot;. Every online business probably comes up first in Google for their own name. (If you don&#039;t, you have larger problems and you should probably address those).&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what I consider, if not a &quot;black hat&quot; PPC technique, a grey one which we&#039;re not interested in because it costs us affiliate commissions on sales we would have gotten without the affiliate ever being involved. Here&#039;s how the scam works: &lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/227-Running-an-affiliate-program-Dont-pay-for-sales-you-already-had-in-the-bag.html#extended&quot;&gt;Continue reading &quot;Running an affiliate program? Don&#039;t pay for sales you already had in the bag&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 27 Aug 2008 11:31:29 -0400</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/227-guid.html</guid>
    
</item>
<item>
    <title>How to use your own domain name with Google Apps</title>
    <link>http://blog.easydns.org/archives/196-How-to-use-your-own-domain-name-with-Google-Apps.html</link>
            <category>Tips and Tricks</category>
    
    <comments>http://blog.easydns.org/archives/196-How-to-use-your-own-domain-name-with-Google-Apps.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=196</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=196</wfw:commentRss>
    

    <author>nospam@example.com (Mark Jeftovic)</author>
    <content:encoded>
    Many Ayromlou does it again, publishing another step-by-step tutorial, complete with screen shots on &lt;a href=&quot;http://www.nerdlogger.com/2008/03/how-to-setup-easydns-to-work-with.html&quot;&gt;how to use your own domain name on easyDNS with Google Apps.&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Sun, 02 Mar 2008 18:40:09 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/196-guid.html</guid>
    
</item>
<item>
    <title>How to use your domain name with blogger</title>
    <link>http://blog.easydns.org/archives/140-How-to-use-your-domain-name-with-blogger.html</link>
            <category>Tips and Tricks</category>
    
    <comments>http://blog.easydns.org/archives/140-How-to-use-your-domain-name-with-blogger.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=140</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=140</wfw:commentRss>
    

    <author>nospam@example.com (Mark Jeftovic)</author>
    <content:encoded>
    Title says it all, easyDNS member Many Ayromlou wrote a clear step-by-step mini-howto today explaining the procedure to get your domain name registered through us working with your blogger.com blog:&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.nerdlogger.com/2007/05/how-to-use-custom-dns-name-with-blogger.html&quot;  title=&quot;How to use your domain name with blogger&quot;&gt;http://www.nerdlogger.com/2007/05/how-to-use-custom-dns-name-with-blogger.html&lt;br /&gt;
&lt;/a&gt;&lt;br /&gt;
My only comment is Step 6 shouldn&#039;t be a few hours&#039; wait, not unless you&#039;ve already typed your domain name into your browser &lt;i&gt;before&lt;/i&gt; you do this and now your local ISP&#039;s nameservers have cached your old IP. &lt;br /&gt;
&lt;br /&gt;
But thanks to Many, I&#039;m sure a lot of bloggers interested on using their own domain name with blogger.com will reference this. 
    </content:encoded>

    <pubDate>Thu, 31 May 2007 20:52:35 -0400</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/140-guid.html</guid>
    
</item>
<item>
    <title>Four essential components of Search Engine Optimization</title>
    <link>http://blog.easydns.org/archives/118-Four-essential-components-of-Search-Engine-Optimization.html</link>
            <category>Tips and Tricks</category>
    
    <comments>http://blog.easydns.org/archives/118-Four-essential-components-of-Search-Engine-Optimization.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=118</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=118</wfw:commentRss>
    

    <author>nospam@example.com (Mark Jeftovic)</author>
    <content:encoded>
    I&#039;ve been helping a longtime customer debug getting his website setup with a &lt;a href=&quot;http://www.google.com/webmasters/sitemaps&quot;&gt;google sitemap&lt;/a&gt; and stealth redirection and he asked me in more general terms if I had any advice for him around search engine optimization.&lt;br /&gt;
&lt;br /&gt;
Here are four essential &quot;must have&#039;s&quot; for SEO. Three you can do right now, the fourth is not under your control as much. Before embarking on a concentrated SEO campaign, be sure the first three are in place.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/118-Four-essential-components-of-Search-Engine-Optimization.html#extended&quot;&gt;Continue reading &quot;Four essential components of Search Engine Optimization&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 06 Dec 2006 13:02:39 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/118-guid.html</guid>
    
</item>
<item>
    <title>Want to reduce email spam to your mail server? Stop using backup spooling</title>
    <link>http://blog.easydns.org/archives/87-Want-to-reduce-email-spam-to-your-mail-server-Stop-using-backup-spooling.html</link>
            <category>Tips and Tricks</category>
    
    <comments>http://blog.easydns.org/archives/87-Want-to-reduce-email-spam-to-your-mail-server-Stop-using-backup-spooling.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=87</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=87</wfw:commentRss>
    

    <author>nospam@example.com (Mark Jeftovic)</author>
    <content:encoded>
    It is with regret that we have come to the following conclusion, but here it is: &lt;b&gt;Offsite backup SMTP spoolers and backup mail exchangers have become worse than useless&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
The problem is spam and the software that delivers it exploiting the weak authentication schemes inherent in the SMTP protocol itself. It used to be an annoyance, then it became a concern, it is now an epidemic and has resulted in the death of the offsite backup MX handler.&lt;br /&gt;
&lt;br /&gt;
What happens is this: spammers try &quot;dictionary attacks&quot; on target domain names, trying to deliver email messages at random usernames at the target domain. The primary mailserver knows which usernames are valid and rejects the rest. The offsite backup MX spooler doesn&#039;t know what usernames are valid and what are junk, so it just forwards everything it receives for a domain it is spooling for to the primary MX handler.&lt;br /&gt;
&lt;br /&gt;
Spammers and other malicious parties know this, so they may not even bother trying the primary MX at all, they&#039;ll just throw everything at the backup mail spooler which dutifully forwards it all (or tries to) to the primary. It is a dead-easy method of launching a Denial-Of-Service attack as well.&lt;br /&gt;
&lt;br /&gt;
So it is with a heavy heart we have to admit that any utility of having an offsite backup MX handler is in most cases far outweighed by the advantages it hands to spammers and other miscreants.&lt;br /&gt;
&lt;br /&gt;
The good news is this: without a backup mail spooler defined for your domain, originating mail servers simply queue the mail locally for a later retry. So owing to the design of the SMTP protocol, you do not really lose any redundancy when you remove a backup MX spooler from your DNS settings. But you probably cut down on the amount of spam your domain receives through the back door that is the backup MX spooler.&lt;br /&gt;
   
    </content:encoded>

    <pubDate>Tue, 27 Jun 2006 16:33:57 -0400</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/87-guid.html</guid>
    
</item>

</channel>
</rss>