<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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/"
	>

<channel>
	<title>LAMPdocs: Linux, Apache, MySQL, PHP &#187; DNS Entries</title>
	<atom:link href="http://www.lampdocs.com/blog/category/dns-entries/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lampdocs.com/blog</link>
	<description>Linux, Apache, MySQL, PHP: Docs, Tricks and Secrets</description>
	<lastBuildDate>Wed, 28 Jul 2010 08:36:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>How to Use Dynamic DNS With a PPP Connection in Linux</title>
		<link>http://www.lampdocs.com/blog/2010/02/how-to-use-dynamic-dns-with-a-ppp-connection-in-linux/</link>
		<comments>http://www.lampdocs.com/blog/2010/02/how-to-use-dynamic-dns-with-a-ppp-connection-in-linux/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 18:04:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DNS Entries]]></category>
		<category><![CDATA[Linux Tricks]]></category>
		<category><![CDATA[allow dyndns requests]]></category>
		<category><![CDATA[bind dynamic dns]]></category>
		<category><![CDATA[ddns pppd]]></category>
		<category><![CDATA[dynamic dns iptables]]></category>
		<category><![CDATA[dynamic dns setup]]></category>
		<category><![CDATA[dynamic dns setup pppd]]></category>
		<category><![CDATA[inadyn configuration]]></category>
		<category><![CDATA[inadyn dyndns]]></category>
		<category><![CDATA[inadyn setup linux]]></category>

		<guid isPermaLink="false">http://www.lampdocs.com/blog/?p=838</guid>
		<description><![CDATA[Dynamic dns is simple! Just follow our guide to setup it in Linux. ]]></description>
			<content:encoded><![CDATA[<p>Dynamic DNS represents a DNS management system, that allows to periodically update DNS records. Since almost any DNS server provides this functionality, dynamic DNS is used when updates need to be more frequent than usually and updated DNS becomes the most important point in user activity (more than speed, system stability, etc).</p>
<p>When you need to establish connection with a hostname, that has a dynamic IP address (most typical situation &#8211; a hostname, that has an unstable Internet connection), Dynamic DNS becomes a simple yet stable solution.</p>
<p>When a hostname obtains an IP address, it is automatically sent to Dynamic DNS system, but users are able to connect using a symbolic name, that remains unchanged (for example, hostname.com).  In order to prevent IP caching, Dynamic DNS records have low TTL values (e.g. 60 seconds).</p>
<p>We&#8217;re going to cover the process of using such a configuration with a pppd connection, this package is widely used in Linux with almost all types of Internet connections.</p>
<p>We will take <a href="http://www.dyndns.com/">dyndns.org</a> as a Dynamic DNS provider (you&#8217;re welcome to select another one: there is no real difference between them). We won&#8217;t describe the process of signing up and creating DNS records, but you&#8217;re always welcome to follow <a href="http://www.dyndns.com/services/dns/dyndns/howto.html">this guide</a>, and ask us if anything is unclear, though it should be.</p>
<p>We will use<a href="http://www.inatech.eu/inadyn/"> inadyn</a> for our connections. It gives the possibility to have your own fixed hostname registered on the internet, although your IP might be changing. It checks periodically whether the IP address stored by the DNS server is the real current IP address of the machine that is running INADYN. Though there are some limitations, that are described <a href="http://www.dyndns.com/support/kb/using_inadyn_with_dyndns_services.html">here</a>, it is a simple solution, that doesn&#8217;t require any specific knowledge. It is a free software, that allows to connect with many Dynamic DNS providers, and you can obtain it by following <a href="http://cdn.dyndns.com/inadyn.zip">this link</a>.</p>
<p>You will need to download it, unpack and compile using <strong>make</strong>.</p>
<p>We will use it in the following way:</p>
<p>inadyn is started when the connection is being established (pppd acquires an IP address and creates an interface). Immediately after that it tries to perform an update and then remains in memory to periodically check for updates. If inadyn is already present in memory, it will be terminated before running a new instance.</p>
<p>In order to do that, we need to touch /etc/ppp/ip-up.local file (create a new one if it doesn&#8217;t exist) with the following contents:</p>
<blockquote><p>#!/bin/sh<br />
kill `ps -A |grep inadyn |sed &#8216;s/[ |\t].*$//&#8217;`<br />
sleep 1<br />
/etc/ppp/inadyn -u <strong>login</strong> -p <strong>xxxxx </strong>-a <strong>lampdocs.dyndns.org</strong> &#8211;background &#8211;update_period_sec 3600</p></blockquote>
<p>Replace <strong>xxxxx </strong>with your password, <strong>login </strong>with your username, obtained at dyndns.org and <strong>lampdocs.dyndns.org</strong> with a symbolic name you&#8217;ve set for your host with dynamic IP.</p>
<p>You can change kill `ps -A |grep inadyn |sed &#8216;s/[ |\t].*$//&#8217;` if you don&#8217;t like it. Here is another variant:</p>
<blockquote><p>#!/bin/sh<br />
pkill inadyn<br />
sleep 1<br />
/etc/ppp/inadyn -u login -p xxxxx -a lampdocs.dyndns.org &#8211;background &#8211;update_period_sec 3600</p></blockquote>
<p>That&#8217;s enough for configuration. Inadyn will be automatically started when a new pppd connection is established. You might need to enable inadyn requests in firewall, so it could connect using http without any problems. Inadyn requires just 2 addresses to connect, and both of them have fixed IPs:</p>
<blockquote><p>checkip.dyndns.org (IP 208.78.70.70)<br />
members.dyndns.org (IP 204.13.248.112)</p></blockquote>
<p>You can enable these requests by issuing the following commands:</p>
<blockquote><p>iptables -t filter -I OUTPUT -p tcp -d 208.78.70.70 &#8211;destination-port 80 -j ACCEPT<br />
iptables -t filter -I OUTPUT -p tcp -d 204.13.248.112 &#8211;destination -port 80 -j ACCEPT</p></blockquote>
<p>Then you should input</p>
<blockquote><p>iptables -t filter -I INPUT -p tcp -s 208.78.70.70 &#8211;source-port 80 -j ACCEPT<br />
iptables -t filter -I INPUT -p tcp -s 204.13.248.112 &#8211;source-port 80 -j ACCEPT</p></blockquote>
<p>Or</p>
<blockquote><p>iptables -t filter -I INPUT -m state &#8211;state ESTABLISHED,RELATED -j ACCEPT</p></blockquote>
<p>- they have the same functionality for our needs. That&#8217;s all, Dynamic DNS should be working for you. Note, that you will have to configure inadyn if you choose another Dynamic DNS provider, the configuration is not complicated and you can find it in inadyn documentation.</p>
<p>Please, let us know if you have any problems using Dynamic DNS.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.lampdocs.com/blog/2010/02/how-to-use-dynamic-dns-with-a-ppp-connection-in-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Disable Dynamic DNS Update in bind</title>
		<link>http://www.lampdocs.com/blog/2010/01/how-to-disabe-dynamic-dns-update-in-bind/</link>
		<comments>http://www.lampdocs.com/blog/2010/01/how-to-disabe-dynamic-dns-update-in-bind/#comments</comments>
		<pubDate>Sat, 30 Jan 2010 08:48:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DNS Entries]]></category>
		<category><![CDATA[bind disable dynamic dns]]></category>
		<category><![CDATA[bind secure configuration]]></category>
		<category><![CDATA[disable dns updates in bind]]></category>
		<category><![CDATA[dns update disable]]></category>

		<guid isPermaLink="false">http://www.lampdocs.com/blog/?p=817</guid>
		<description><![CDATA[How to disable dynamic dns updates in bind. Just a single string added to named.conf]]></description>
			<content:encoded><![CDATA[<p>First of all, let&#8217;s figure out what Dynamic DNS update is and why it is used in most recent versions of bind. </p>
<p>Dynamic update represents the idea of exchanging data between two computers with known names both visiting an unknown network where we don&#8217;t know, care or trust the underlying address. </p>
<p>It is now possible to point your neighbor at the IETF conference to a web page on your laptop by pointing at the URL on your business card using this technology.</p>
<p>When this feature is enabled, your computer has a potential vulnerability, if your bind configuration is secured using TSIG keys or SIG(0). I will create a post on this subject a bit later, but now I&#8217;m going to tell you how to disable Dynamic Updates, if you are unsure whether they are secure.  </p>
<p>We need to edit named.conf using any editor available. For each domain zone, that should be secured, we need to add a string. Let me show you how to do it. Here is my zone config before: </p>
<blockquote><p>zone &#8220;lampdocs.com&#8221; { type master; file &#8220;/var/named/lampdocs.com.db&#8221;; };</p></blockquote>
<p>We&#8217;re adding a line to disable dynamic DNS updates: </p>
<blockquote><p>zone &#8220;lampdocs.com&#8221; { type master; file &#8220;/var/named/lampdocs.com.db&#8221;;<br />
allow-update { none; };<br />
 };</p></blockquote>
<p>That&#8217;s all. Now Dynamic DNS updates are disabled for your domain. Don&#8217;t forget to restart bind to activate your input. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.lampdocs.com/blog/2010/01/how-to-disabe-dynamic-dns-update-in-bind/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What to Do If Domain is Not Resolving at All</title>
		<link>http://www.lampdocs.com/blog/2008/09/what-to-do-if-domain-is-not-resolving-at-all/</link>
		<comments>http://www.lampdocs.com/blog/2008/09/what-to-do-if-domain-is-not-resolving-at-all/#comments</comments>
		<pubDate>Mon, 08 Sep 2008 08:03:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DNS Entries]]></category>
		<category><![CDATA[domain not resolving]]></category>
		<category><![CDATA[domain not resolving change dns]]></category>

		<guid isPermaLink="false">http://www.lampdocs.com/blog/?p=163</guid>
		<description><![CDATA[I&#8217;ve met this several times in my career. It is hard to explain, but this the only working solution I found for such issues. Let me tell you about the situation: You&#8217;ve registered a new domain and pointed to correct DNS servers. Everything seems to be nice: an account at your hosting is created too. [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve met this several times in my career. It is hard to explain, but this the only working solution I found for such issues. Let me tell you about the situation:</p>
<p>You&#8217;ve registered a new domain and pointed to correct DNS servers. Everything seems to be nice: an account at your hosting is created too. You&#8217;re sitting and waiting for DNS to start resolving&#8230;</p>
<p>But after two or three days your fresh domain is still not accessible. You&#8217;re trying to contact hosting support and domain registrar support, but both are telling you that everything is set up and you just have to wait. But you may wait as long as you want; if your domain does not resolve within 2-3 days, it won&#8217;t resolve at all. And you have to do a simple trick that worked for me.</p>
<p>You need to have a hosting service to create an account for your lost domain. You won&#8217;t need it more than several hours, so you may just ask one of your friends who have an account with unlimited domains to host your domain for 3 hours.</p>
<p>All you need is to create an account for your domain and change DNS to another server, then you should wait until your domain resolves. Once it starts responging, you should change your DNS back to previous values. I can almost guarantee you it will be resolving to new DNS in just some minutes.</p>
<p>Don&#8217;t ask me why does this work as I really have no idea. Just like Windows reboot &#8211; often helps but you cannot explain why. <img src='http://www.lampdocs.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.lampdocs.com/blog/2008/09/what-to-do-if-domain-is-not-resolving-at-all/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
