<?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>bind &#8211; VeriTeknik</title>
	<atom:link href="https://www.veriteknik.net.tr/en/tag/bind/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.veriteknik.net.tr/en/</link>
	<description>VeriTeknik Bilişim &#124; VeriTeknik Bilişim</description>
	<lastBuildDate>Wed, 02 May 2012 10:03:38 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Bind Multiple IP Addresses on a Single Network Card IPv4 &#038; IPv6</title>
		<link>https://www.veriteknik.net.tr/en/bind-multiple-ip-addresses-on-a-single-network-card/</link>
					<comments>https://www.veriteknik.net.tr/en/bind-multiple-ip-addresses-on-a-single-network-card/#respond</comments>
		
		<dc:creator><![CDATA[Mustafa Emre Aydın]]></dc:creator>
		<pubDate>Wed, 02 May 2012 10:03:38 +0000</pubDate>
				<category><![CDATA[LINUX]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[bind]]></category>
		<category><![CDATA[ip]]></category>
		<category><![CDATA[ipv4]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[network]]></category>
		<guid isPermaLink="false">http://www.plugged.in/?p=366</guid>

					<description><![CDATA[<p>The beauty of having multiple IP addresses on a single server is that you can run several services with different addressing. This way you can announce your FTP service on a different address and your HTTP on another. Below I&#8217;ll describe how to achieve this in Debian based and Red Hat based distros seperately. Using [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.veriteknik.net.tr/en/bind-multiple-ip-addresses-on-a-single-network-card/">Bind Multiple IP Addresses on a Single Network Card IPv4 &#038; IPv6</a> appeared first on <a rel="nofollow" href="https://www.veriteknik.net.tr/en/">VeriTeknik</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The beauty of having multiple IP addresses on a single server is that you can run several services with different addressing. This way you can announce your FTP service on a different address and your HTTP on another.</p>
<p>Below I&#8217;ll describe how to achieve this in Debian based and Red Hat based distros seperately.</p>
<p>Using Debian based distros (Ubuntu, Mint etc.), setting multiple IP addresses on a single network interface is simple.</p>
<p>What we will do is to edit the /etc/network/interfaces file.<br />
If you are using DHCP, then your file should look similar to this,</p>
<pre class="brush: text; gutter: true; first-line: 1">auto eth0
iface eth0 inet dhcp

auto eth0:0
iface eth0:0 inet dhcp
iface eth0:0 inet6 dhcp</pre>
<p>Here, the <strong>eth0:0</strong> is how we get the secondary IP address on the <strong>eth0</strong> device.</p>
<p>If you&#8217;re using a static IP address instead of DHCP, then your interfaces file should be like,</p>
<pre class="brush: text; gutter: true; first-line: 1">auto eth0
iface eth0 inet static
address 10.20.30.40
netmask 255.255.255.0
network 10.20.30.0
broadcast 10.20.30.255
gateway 10.20.30.1
dns-nameservers 8.8.8.8

iface eth0 inet6 static
address 2f00:7300:100::10
netmask 64

auto eth0:0
iface eth0:0 inet static
address 10.20.30.41
netmask 255.255.255.0

iface eth0:0 inet6 static
address 2f00:7300:100::11
netmask 64</pre>
<p>You can add as many as you want, such as <strong>eth0:1</strong>, <strong>eth0:2</strong> &#8230;</p>
<p>Sometimes when adding multiple IPv6 addresses on Debian systems, it is possible that you get an error. The current workaround for that is to enable and disable the device a couple of times. You can find the solution to that problem <a href="https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/617978" target="_blank">here</a>.</p>
<p>In Red Hat based distros (CentOS, Fedora etc.), the interfaces are edited through the directory <strong>/etc/sysconfig/network-scritps</strong>. Here we have multiple files, each pointing for a device. For instance, to have 2 additional IP&#8217;s on a single ethernet device (totaling 3 addresses) we should have 3 files as follows,</p>
<p><strong>/etc/sysconfig/network-scripts/ifcfg-eth0<br />
/etc/sysconfig/network-scripts/ifcfg-eth0:1<br />
/etc/sysconfig/network-scripts/ifcfg-eth0:2</strong></p>
<p>The main device file would be just a standard one, we don&#8217;t have to change anything with it.<br />
On the other hand, the <strong>ifcfg-eth0:1</strong> file should be similar to this,</p>
<pre class="brush: text; gutter: true; first-line: 1">NAME=""
BOOTPROTO=static
MACADDR=""
IPV6INIT=no
DEVICE=eth0:1
NETMASK=255.255.255.0
MTU=""
BROADCAST=10.20.30.255
ONPARENT=yes
IPADDR=10.20.30.41
NETWORK=10.20.30.0
IPV6INIT=yes
IPV6ADDR=2f00:7300:100::11
IPV6_DEFAULTGW=2f00:7300:100::1
ONBOOT=yes</pre>
<p>This would suffice. Don&#8217;t forget to restart your network services after adding the lines (or files) to with your appropriate settings.</p>
<p>For Debian : <strong>$ /etc/init.d/networking stop &amp;&amp; /etc/init.d/networking start</strong><br />
For Red Hat : <strong>$ service network restart</strong></p>
<p>For additional IPv6 addresses you should need to add IPV6ADDR_SECONDARIES=&#8221;&#8221; line to /etc/sysconfig/network-scripts/ifcfg-eth0 file</p>
<pre class="brush: text; gutter: true; first-line: 1">IPV6INIT=yes
IPV6ADDR=2f00:7300:1::2/64
IPV6ADDR_SECONDARIES="2f00:7300:1::3/64 2f00:7300:1::4/64 2f00:7300:1::fff4/64 2f00:7300:1::fff5/64"</pre>
<p>The post <a rel="nofollow" href="https://www.veriteknik.net.tr/en/bind-multiple-ip-addresses-on-a-single-network-card/">Bind Multiple IP Addresses on a Single Network Card IPv4 &#038; IPv6</a> appeared first on <a rel="nofollow" href="https://www.veriteknik.net.tr/en/">VeriTeknik</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.veriteknik.net.tr/en/bind-multiple-ip-addresses-on-a-single-network-card/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">366</post-id>	</item>
		<item>
		<title>Disabling recursive queries in Bind</title>
		<link>https://www.veriteknik.net.tr/en/disabling-recursive-queries-in-bind/</link>
					<comments>https://www.veriteknik.net.tr/en/disabling-recursive-queries-in-bind/#respond</comments>
		
		<dc:creator><![CDATA[ckaraca]]></dc:creator>
		<pubDate>Sat, 23 Apr 2011 22:24:29 +0000</pubDate>
				<category><![CDATA[LINUX Help]]></category>
		<category><![CDATA[bind]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[named]]></category>
		<category><![CDATA[query]]></category>
		<category><![CDATA[recursive]]></category>
		<guid isPermaLink="false">http://www.plugged.in/?p=37</guid>

					<description><![CDATA[<p>If you own your DNS servers, you should probably want to close recursive queries being gathered from your servers. In named.conf edit the options directive and add: options { allow-transfer {Secondary Server IP; }; allow-recursion { 127.0.0.1; A.B.C/24; }; }; In secondary server: add to options: allow-transfer { none; }; allow-recursion { 127.0.0.1; A.B.C/24; };</p>
<p>The post <a rel="nofollow" href="https://www.veriteknik.net.tr/en/disabling-recursive-queries-in-bind/">Disabling recursive queries in Bind</a> appeared first on <a rel="nofollow" href="https://www.veriteknik.net.tr/en/">VeriTeknik</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If you own your DNS servers, you should probably want to close recursive queries being gathered from your servers.</p>
<p>In named.conf edit the options directive and add:</p>
<blockquote><p>options {</p>
<p style="padding-left: 30px;">allow-transfer {Secondary Server IP; }; allow-recursion { 127.0.0.1; A.B.C/24; };</p>
<p>};</p></blockquote>
<p>In secondary server:<br />
add to options:</p>
<blockquote><p>allow-transfer { none; }; allow-recursion { 127.0.0.1; A.B.C/24; };</p></blockquote>
<p>The post <a rel="nofollow" href="https://www.veriteknik.net.tr/en/disabling-recursive-queries-in-bind/">Disabling recursive queries in Bind</a> appeared first on <a rel="nofollow" href="https://www.veriteknik.net.tr/en/">VeriTeknik</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.veriteknik.net.tr/en/disabling-recursive-queries-in-bind/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">37</post-id>	</item>
	</channel>
</rss>
