<![CDATA[Linux-Noob Forums - DNS and DHCP]]> https://www.linux-noob.com/forums/ Thu, 07 May 2026 21:06:08 +0000 MyBB <![CDATA[New to linux]]> https://www.linux-noob.com/forums/thread-382.html Wed, 13 Apr 2011 11:41:51 +0200 Jaxzu]]> https://www.linux-noob.com/forums/thread-382.html hey guys

 

i have a problem i am new to linux and i want to configure a Dns server for mail and web hosting but i am having an error when i try to start my name server. i have editted my named.conf file this is how it looks like

 

Error

Starting named:

Error in named configuration:

zone aromotorgroup.com/IN: loaded serial 2010052601

zone 1.168.192.in-addr.arpa/IN: loaded serial 2010052601

zone localhost.localdomain/IN: loaded serial 0

zone localhost/IN: loaded serial 0

zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0

zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0

zone 0.in-addr.arpa/IN: loaded serial 0

zone aromotorgroup.com/IN: loading from master file aromotorgroup.com failed: file not found

zone aromotorgroup.com/IN: not loaded due to errors.

external/aromotorgroup.com/IN: file not found

zone 226.99.221.41.in-addr.arpa/IN: loaded serial 2010052601

[FAILED]

 

my named.conf file looks like this

//

// named.conf

//

// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS

// server as a caching only nameserver (as a localhost DNS resolver only).

//

// See /usr/share/doc/bind*/sample/ for example named configuration files.

//

 

options {

#listen-on port 53 { 127.0.0.1; };

#listen-on-v6 port 53 { ::1; };

directory "/var/named";

dump-file "/var/named/data/cache_dump.db";

statistics-file "/var/named/data/named_stats.txt";

memstatistics-file "/var/named/data/named_mem_stats.txt";

allow-query { localhost;192.168.1.100/24; };

recursion yes;

 

dnssec-enable yes;

dnssec-validation yes;

dnssec-lookaside auto;

allow-transfer { localhost; 192.168.1.0/24; };

/* Path to ISC DLV key */

bindkeys-file "/etc/named.iscdlv.key";

};

 

logging {

channel default_debug {

file "data/named.run";

severity dynamic;

};

};

view "internal" {

match-clients {

localhost;

192.168.1.0/24;

};

zone "." IN {

type hint;

file "named.ca";

};

zone "aromotorgroup.com" IN {

type master;

file "aromotorgroup.com.lan";

allow-update { none; };

};

zone "1.168.192.in-addr.arpa" IN {

type master;

file "1.168.192.db";

allow-update { none; };

};

include "/etc/named.rfc1912.zones";

};

view "external" {

match-clients {

any;

};

zone "." IN {

type hint;

file "named.ca";

};

zone "aromotorgroup.com" IN {

type master;

file "aromotorgroup.com";

allow-update { none; };

};

zone "226.99.221.41.in-addr.arpa" IN {

 

 

type master;

file "226.99.221.41.db";

allow-update { none; };

};

};

and my zone file looks like this

 

$TTL 86400

@ IN SOA localhost.aromotorgroup.com. root.aromotorgroup.com. (

2004042801 ; Serial

2H ; Refresh

2H ; Retry

1H ; Expire

1D) ; Min TTL

 

NS localhost.aromotorgroup.com.

NS ns.domain.com.

 

aromotorgroup.com. MX 5 mail.jyrules.com.

aromotorgroup.com. MX 15 pvr.jyrules.com.

 

aromotorgroup.com. A 41.221.99.226

 

localhost A 127.0.0.1

 

www CNAME aromotorgroup.com.

ftp CNAME aromotorgroup.com.

mail CNAME aromotorgroup.com.

 

pvr IN A 226.99.221.41

 

i hope i will be helped

 

 

Thanks

]]> hey guys

 

i have a problem i am new to linux and i want to configure a Dns server for mail and web hosting but i am having an error when i try to start my name server. i have editted my named.conf file this is how it looks like

 

Error

Starting named:

Error in named configuration:

zone aromotorgroup.com/IN: loaded serial 2010052601

zone 1.168.192.in-addr.arpa/IN: loaded serial 2010052601

zone localhost.localdomain/IN: loaded serial 0

zone localhost/IN: loaded serial 0

zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0

zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0

zone 0.in-addr.arpa/IN: loaded serial 0

zone aromotorgroup.com/IN: loading from master file aromotorgroup.com failed: file not found

zone aromotorgroup.com/IN: not loaded due to errors.

external/aromotorgroup.com/IN: file not found

zone 226.99.221.41.in-addr.arpa/IN: loaded serial 2010052601

[FAILED]

 

my named.conf file looks like this

//

// named.conf

//

// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS

// server as a caching only nameserver (as a localhost DNS resolver only).

//

// See /usr/share/doc/bind*/sample/ for example named configuration files.

//

 

options {

#listen-on port 53 { 127.0.0.1; };

#listen-on-v6 port 53 { ::1; };

directory "/var/named";

dump-file "/var/named/data/cache_dump.db";

statistics-file "/var/named/data/named_stats.txt";

memstatistics-file "/var/named/data/named_mem_stats.txt";

allow-query { localhost;192.168.1.100/24; };

recursion yes;

 

dnssec-enable yes;

dnssec-validation yes;

dnssec-lookaside auto;

allow-transfer { localhost; 192.168.1.0/24; };

/* Path to ISC DLV key */

bindkeys-file "/etc/named.iscdlv.key";

};

 

logging {

channel default_debug {

file "data/named.run";

severity dynamic;

};

};

view "internal" {

match-clients {

localhost;

192.168.1.0/24;

};

zone "." IN {

type hint;

file "named.ca";

};

zone "aromotorgroup.com" IN {

type master;

file "aromotorgroup.com.lan";

allow-update { none; };

};

zone "1.168.192.in-addr.arpa" IN {

type master;

file "1.168.192.db";

allow-update { none; };

};

include "/etc/named.rfc1912.zones";

};

view "external" {

match-clients {

any;

};

zone "." IN {

type hint;

file "named.ca";

};

zone "aromotorgroup.com" IN {

type master;

file "aromotorgroup.com";

allow-update { none; };

};

zone "226.99.221.41.in-addr.arpa" IN {

 

 

type master;

file "226.99.221.41.db";

allow-update { none; };

};

};

and my zone file looks like this

 

$TTL 86400

@ IN SOA localhost.aromotorgroup.com. root.aromotorgroup.com. (

2004042801 ; Serial

2H ; Refresh

2H ; Retry

1H ; Expire

1D) ; Min TTL

 

NS localhost.aromotorgroup.com.

NS ns.domain.com.

 

aromotorgroup.com. MX 5 mail.jyrules.com.

aromotorgroup.com. MX 15 pvr.jyrules.com.

 

aromotorgroup.com. A 41.221.99.226

 

localhost A 127.0.0.1

 

www CNAME aromotorgroup.com.

ftp CNAME aromotorgroup.com.

mail CNAME aromotorgroup.com.

 

pvr IN A 226.99.221.41

 

i hope i will be helped

 

 

Thanks

]]> <![CDATA[Set up a simple DHCP server for a small network]]> https://www.linux-noob.com/forums/thread-510.html Tue, 23 Feb 2010 20:22:59 +0100 hybrid]]> https://www.linux-noob.com/forums/thread-510.html A while back, an upgrade to the firmware of the router on my local network (which I wanted to apply to enable WPA2 encryption for the wireless connection) starting causing some strange issues with clients connecting to the network with DHCP. They would get addresses which would work, but when the addresses were attempted to be renewed, the DHCP server in the router would refuse and the client would effectively be booted off the network and unable to access anything.

 

So I decided to set up a DHCP server on my web server machine and switch off the built-in DHCP server on the router. My server would now handle the assignment of addresses, and hopefully not suffer from this annoying bug!

 

So, here's how to configure a basic DHCP server for a local network with dhcpd on CentOS 5.3. This guide should work for pretty much any distribution, though, just the way you install the dhcpd package may be different and start and stop the server may differ somewhat.

 

Install dhcpd

 

First, you need to install the DHCP server package. As root, run:

 



Code:
yum install dhcp




 

Just one more thing before we get cracking -- make sure that the server where you are installing this DHCP server uses a static IP address. It obviously doesn't make any sense for it to get its IP address from itself. I'm assuming you have a machine here that is designated as a server that is already set up manually to connect to your local network with a static IP address.

 

Set up the configuration file

 

You will need to know the local IP address range of your local network and which addresses you want to be assigned via DHCP. If you have some machines that are assigned static IP addresses, make sure these addresses fall outside the scope of your DHCP address range, or you could create conflicts.

 

In this example, I am going to assign IP addresses from 192.168.1.64 through 192.168.1.250 as DHCP addresses. When a machine comes on to the network, it will be assigned an address in this range by my new DHCP server. The router IP address on this network is 192.168.1.1.

 

Open the /etc/dhcpd.conf file in your favourite editor, while running as root. Make your file look something like this:

 



Code:
#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#

ddns-update-style none;
ignore client-updates;
# these two options are for allowing clients to tell
# update a DNS server when DHCP clients want a DNS hostname.
# I'm switching this off -- I don't need it and it's out of
# the scope of this tutorial!

option domain-name-servers 216.146.35.35, 216.146.36.36;
# place your DNS servers here -- you will probably want to retrieve
# the addresses of the DNS servers you currently use from your router.
# Here I'm using the public DNS servers of the Dyn Internet Guide public
# DNS service. You may prefer your ISP's servers, or OpenDNS or Google Public
# DNS or another service.

default-lease-time 172800; # one day
max-lease-time 604800; # seven days
# you should be fine with these, unless you specifically want to change them!

authoritative;

subnet 192.168.1.0 netmask 255.255.255.0 {
# place your network's IP information here, you should be able to retrieve from
# your router.

range                    192.168.1.64 192.168.1.250;
# the range of addresses to be used by DHCP clients
option routers           192.168.1.1;
# the IP of your router, in order to get traffic out to the internet!
option subnet-mask       255.255.255.0
# again, retrieve from your current settings
option broadcast-address 192.168.1.255
# usually the last address on your network, again look at your current settings


}




 

You will obviously need to substitute into that example file the IP addresses on your network, including the subnet, your desired IP address range for DHCP users, the router and your preferred DNS servers. As the comments say, you should be able to retrieve most of this information from your current network setup; so it will probably be on the pages of your router's configuration web page.

 

When you have customised that file with your information, save the file and quit your editor. The DHCP server should now be ready for action.

 

Start the DHCP server and set to run on reboot

 

Now, stop any existing DHCP server you might have enabled on your router. You will probably have to go to the configuration web page of your router and disable the DHCP server option. Two DHCP servers on the same network will likely conflict unless set up properly to coexist!

 

Note that while there is no DHCP server on your network, any machine that joins won't be able to get an IP address and therefore will have trouble doing anything. Best do this at a quiet time when no-one is likely to be switching on or restarting their computer or otherwise reconnecting to your network.

 

Now switch on your new DHCP server if it isn't already. As root:

 



Code:
/etc/init.d/dhcpd start




 

You may want to use something 'Repair Connection' or a forced network refresh on one of your client computers to test that the new DHCP server is giving out addresses properly. Check the network properties on that machine and you should notice it has an address in the right range. To make sure that your router and DNS server addresses are right, connect to the internet and verify you can access your favourite websites.

 

If something goes wrong, use:

 



Code:
/etc/init.d/dhcpd stop
chkconfig dhcpd off




 

to turn off your DHCP server (and prevent it from running again on reboot) and then you can re-enable the router's DHCP server option and be back at square one.

 

If all seems good and your new DHCP server is giving out the right addresses, you can set dhcpd to run at startup:

 



Code:
chkconfig dhcpd on




 

From now on, your new DHCP server on Linux will be responsible for dishing out network addresses to clients.

 

Just remember that this machine where the DHCP server is installed must be switched on in order for the network to function properly. This machine ideally should be left on all the time (or at least all the time that your router is switched on), so that computers on the network can get access to the network properly.

 

It is also a good idea to know how to configure one of your machines with a static IP address, so that if all else fails, you can log back into the router and switch on its DHCP server option again.

]]> A while back, an upgrade to the firmware of the router on my local network (which I wanted to apply to enable WPA2 encryption for the wireless connection) starting causing some strange issues with clients connecting to the network with DHCP. They would get addresses which would work, but when the addresses were attempted to be renewed, the DHCP server in the router would refuse and the client would effectively be booted off the network and unable to access anything.

 

So I decided to set up a DHCP server on my web server machine and switch off the built-in DHCP server on the router. My server would now handle the assignment of addresses, and hopefully not suffer from this annoying bug!

 

So, here's how to configure a basic DHCP server for a local network with dhcpd on CentOS 5.3. This guide should work for pretty much any distribution, though, just the way you install the dhcpd package may be different and start and stop the server may differ somewhat.

 

Install dhcpd

 

First, you need to install the DHCP server package. As root, run:

 



Code:
yum install dhcp




 

Just one more thing before we get cracking -- make sure that the server where you are installing this DHCP server uses a static IP address. It obviously doesn't make any sense for it to get its IP address from itself. I'm assuming you have a machine here that is designated as a server that is already set up manually to connect to your local network with a static IP address.

 

Set up the configuration file

 

You will need to know the local IP address range of your local network and which addresses you want to be assigned via DHCP. If you have some machines that are assigned static IP addresses, make sure these addresses fall outside the scope of your DHCP address range, or you could create conflicts.

 

In this example, I am going to assign IP addresses from 192.168.1.64 through 192.168.1.250 as DHCP addresses. When a machine comes on to the network, it will be assigned an address in this range by my new DHCP server. The router IP address on this network is 192.168.1.1.

 

Open the /etc/dhcpd.conf file in your favourite editor, while running as root. Make your file look something like this:

 



Code:
#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#

ddns-update-style none;
ignore client-updates;
# these two options are for allowing clients to tell
# update a DNS server when DHCP clients want a DNS hostname.
# I'm switching this off -- I don't need it and it's out of
# the scope of this tutorial!

option domain-name-servers 216.146.35.35, 216.146.36.36;
# place your DNS servers here -- you will probably want to retrieve
# the addresses of the DNS servers you currently use from your router.
# Here I'm using the public DNS servers of the Dyn Internet Guide public
# DNS service. You may prefer your ISP's servers, or OpenDNS or Google Public
# DNS or another service.

default-lease-time 172800; # one day
max-lease-time 604800; # seven days
# you should be fine with these, unless you specifically want to change them!

authoritative;

subnet 192.168.1.0 netmask 255.255.255.0 {
# place your network's IP information here, you should be able to retrieve from
# your router.

range                    192.168.1.64 192.168.1.250;
# the range of addresses to be used by DHCP clients
option routers           192.168.1.1;
# the IP of your router, in order to get traffic out to the internet!
option subnet-mask       255.255.255.0
# again, retrieve from your current settings
option broadcast-address 192.168.1.255
# usually the last address on your network, again look at your current settings


}




 

You will obviously need to substitute into that example file the IP addresses on your network, including the subnet, your desired IP address range for DHCP users, the router and your preferred DNS servers. As the comments say, you should be able to retrieve most of this information from your current network setup; so it will probably be on the pages of your router's configuration web page.

 

When you have customised that file with your information, save the file and quit your editor. The DHCP server should now be ready for action.

 

Start the DHCP server and set to run on reboot

 

Now, stop any existing DHCP server you might have enabled on your router. You will probably have to go to the configuration web page of your router and disable the DHCP server option. Two DHCP servers on the same network will likely conflict unless set up properly to coexist!

 

Note that while there is no DHCP server on your network, any machine that joins won't be able to get an IP address and therefore will have trouble doing anything. Best do this at a quiet time when no-one is likely to be switching on or restarting their computer or otherwise reconnecting to your network.

 

Now switch on your new DHCP server if it isn't already. As root:

 



Code:
/etc/init.d/dhcpd start




 

You may want to use something 'Repair Connection' or a forced network refresh on one of your client computers to test that the new DHCP server is giving out addresses properly. Check the network properties on that machine and you should notice it has an address in the right range. To make sure that your router and DNS server addresses are right, connect to the internet and verify you can access your favourite websites.

 

If something goes wrong, use:

 



Code:
/etc/init.d/dhcpd stop
chkconfig dhcpd off




 

to turn off your DHCP server (and prevent it from running again on reboot) and then you can re-enable the router's DHCP server option and be back at square one.

 

If all seems good and your new DHCP server is giving out the right addresses, you can set dhcpd to run at startup:

 



Code:
chkconfig dhcpd on




 

From now on, your new DHCP server on Linux will be responsible for dishing out network addresses to clients.

 

Just remember that this machine where the DHCP server is installed must be switched on in order for the network to function properly. This machine ideally should be left on all the time (or at least all the time that your router is switched on), so that computers on the network can get access to the network properly.

 

It is also a good idea to know how to configure one of your machines with a static IP address, so that if all else fails, you can log back into the router and switch on its DHCP server option again.

]]> <![CDATA[Set up a simple forwarding-only DNS server]]> https://www.linux-noob.com/forums/thread-653.html Wed, 03 Jun 2009 21:18:25 +0200 hybrid]]> https://www.linux-noob.com/forums/thread-653.html I have absolutely no experience with DNS servers. I understand the principles behind DNS, but the perceived 'scariness' of configuring bind and different zones and such is quite a big issue.

 

I did want to do some experimentation with DNS servers, though, and I've found a very useful and simple tutorial to set up a simple 'forwarding only' server.

 

The tutorial is designed for Red Hat Enterprise Linux (and written by Red Hat), so it worked exactly as in the tutorial when I followed it on my CentOS 5.3 system.

 

Read the tutorial

]]> I have absolutely no experience with DNS servers. I understand the principles behind DNS, but the perceived 'scariness' of configuring bind and different zones and such is quite a big issue.

 

I did want to do some experimentation with DNS servers, though, and I've found a very useful and simple tutorial to set up a simple 'forwarding only' server.

 

The tutorial is designed for Red Hat Enterprise Linux (and written by Red Hat), so it worked exactly as in the tutorial when I followed it on my CentOS 5.3 system.

 

Read the tutorial

]]> <![CDATA[diskless booting troubles]]> https://www.linux-noob.com/forums/thread-1102.html Fri, 09 Nov 2007 01:23:08 +0100 kaushik]]> https://www.linux-noob.com/forums/thread-1102.html I compiled my client kernel to be vm-linuz-2.6.21-prepclient(FC7), where the client was configured to be NFS bootable.

 

I have two network cards on my client node, and both should be configured to run on different networks.

 

If my node is numbered node 2, then eth0 has 192.168.1.2 and eth1 has 192.168.3.2 . Likewise, node 3 has eth0 configured 192.168.1.3 and eth1 is 192.168.3.3 and so on.

 

First, on power on, the client contacts the server using eth0 with a dhcp request, and gets the correct ip configured to it. Subsequently, diskless booting happens through this network. At the time when eth1 is configured, however, the network fails saying "some other host already uses the address 192.168.3.2.". No matter what address I use, it gives the same error.

 

Prior to activating the network service, I have netfs and rpcbind going up.

 

After the system is booted, I tried manually assigning the ip address, using

 

/sbin/ifconfig eth1 192.168.3.2 up

 

But this dosent help. The DHCP server seems to be running ok and the configuration file too looks ok to me.

 

Can anybody help me with this problem?

]]> I compiled my client kernel to be vm-linuz-2.6.21-prepclient(FC7), where the client was configured to be NFS bootable.

 

I have two network cards on my client node, and both should be configured to run on different networks.

 

If my node is numbered node 2, then eth0 has 192.168.1.2 and eth1 has 192.168.3.2 . Likewise, node 3 has eth0 configured 192.168.1.3 and eth1 is 192.168.3.3 and so on.

 

First, on power on, the client contacts the server using eth0 with a dhcp request, and gets the correct ip configured to it. Subsequently, diskless booting happens through this network. At the time when eth1 is configured, however, the network fails saying "some other host already uses the address 192.168.3.2.". No matter what address I use, it gives the same error.

 

Prior to activating the network service, I have netfs and rpcbind going up.

 

After the system is booted, I tried manually assigning the ip address, using

 

/sbin/ifconfig eth1 192.168.3.2 up

 

But this dosent help. The DHCP server seems to be running ok and the configuration file too looks ok to me.

 

Can anybody help me with this problem?

]]> <![CDATA[troubles with script]]> https://www.linux-noob.com/forums/thread-1306.html Wed, 20 Jun 2007 18:31:07 +0200 snake444]]> https://www.linux-noob.com/forums/thread-1306.html when i run the script i get error, log :



Code:
eth1: No such device
IPv6 configuration failed!




the script's code:



Code:
#!/bin/sh
if ! [ -f /proc/net/if_inet6 ]
then echo "IPv6 is not installed!" 1>&2; exit 1; fi
ifconfig sit0 up \
&& ifconfig sit0 inet6 tunnel ::213.121.24.85 \
&& ifconfig sit1 inet6 add 2001:618:400::591:cb1f/128 \
&& route -A inet6 add ::/0 gw fe80::d579:1855 dev sit1 \
&& route -A inet6 add 2000::/3 gw fe80::d579:1855 dev sit1 \
&& ifconfig eth1 up \
&& ifconfig eth1 inet6 add 2001:618:400:b733::/64 \
&& echo 1 > /proc/sys/net/ipv6/conf/all/forwarding \
&& echo 'interface eth1
{
AdvSendAdvert on;
prefix 2001

:618:400:b733::/64
{
  AdvOnLink on;
  AdvAutonomous on;
};
};' > /etc/radvd.conf \
&& /etc/init.d/radvd start \
&& echo "IPv6 configuration completed" || \
{ echo "IPv6 configuration failed!" 1>&2; exit 1; }




 

and when i do ifconfig there is:



Code:
snake@delta:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:E0:4C:77:CD:1D
      inet6 addr: fe80::2e0:4cff:fe77:cd1d/64 Диапазон:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:270656 errors:0 dropped:0 overruns:0 frame:0
      TX packets:250379 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:275446383 (262.6 MiB)  TX bytes:21518725 (20.5 MiB)
      Interrupt:20 Base address:0x2000

lo        Link encap:Local Loopback
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Диапазон:Host
      UP LOOPBACK RUNNING  MTU:16436  Metric:1
      RX packets:84 errors:0 dropped:0 overruns:0 frame:0
      TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:4817 (4.7 KiB)  TX bytes:4817 (4.7 KiB)

ppp0      Link encap:Point-to-Point Protocol
      inet addr:89.1.203.31  P-t-P:212.29.206.60  Mask:255.255.255.255
      UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
      RX packets:269808 errors:0 dropped:0 overruns:0 frame:0
      TX packets:249776 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:3
      RX bytes:269452852 (256.9 MiB)  TX bytes:15987305 (15.2 MiB)

sit0      Link encap:IPv6-in-IPv4
      inet6 addr: ::89.1.203.31/96 Диапазон:Compat
      inet6 addr: ::127.0.0.1/96 Диапазон:Unknown
      UP RUNNING NOARP  MTU:1480  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

sit1      Link encap:IPv6-in-IPv4
      inet6 addr: 2001:618:400::591:cb1f/128 Диапазон:Общий
      inet6 addr: fe80::5901:cb1f/64 Диапазон:Link
      UP POINTOPOINT RUNNING NOARP  MTU:1472  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:0 (0.0 b)  TX bytes:588 (588.0 b)




any ideas how to solve that problem?

i tryed editing the script and changing all eth1 to eth0 because in ifconfig i dont see any eth1 connection but i got error too



Code:
snake@delta:~$ sudo sh LinuxScript.sh
SIOCSIFADDR: File exists
IPv6 configuration failed!




thanks.

]]> when i run the script i get error, log :



Code:
eth1: No such device
IPv6 configuration failed!




the script's code:



Code:
#!/bin/sh
if ! [ -f /proc/net/if_inet6 ]
then echo "IPv6 is not installed!" 1>&2; exit 1; fi
ifconfig sit0 up \
&& ifconfig sit0 inet6 tunnel ::213.121.24.85 \
&& ifconfig sit1 inet6 add 2001:618:400::591:cb1f/128 \
&& route -A inet6 add ::/0 gw fe80::d579:1855 dev sit1 \
&& route -A inet6 add 2000::/3 gw fe80::d579:1855 dev sit1 \
&& ifconfig eth1 up \
&& ifconfig eth1 inet6 add 2001:618:400:b733::/64 \
&& echo 1 > /proc/sys/net/ipv6/conf/all/forwarding \
&& echo 'interface eth1
{
AdvSendAdvert on;
prefix 2001

:618:400:b733::/64
{
  AdvOnLink on;
  AdvAutonomous on;
};
};' > /etc/radvd.conf \
&& /etc/init.d/radvd start \
&& echo "IPv6 configuration completed" || \
{ echo "IPv6 configuration failed!" 1>&2; exit 1; }




 

and when i do ifconfig there is:



Code:
snake@delta:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:E0:4C:77:CD:1D
      inet6 addr: fe80::2e0:4cff:fe77:cd1d/64 Диапазон:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:270656 errors:0 dropped:0 overruns:0 frame:0
      TX packets:250379 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:275446383 (262.6 MiB)  TX bytes:21518725 (20.5 MiB)
      Interrupt:20 Base address:0x2000

lo        Link encap:Local Loopback
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Диапазон:Host
      UP LOOPBACK RUNNING  MTU:16436  Metric:1
      RX packets:84 errors:0 dropped:0 overruns:0 frame:0
      TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:4817 (4.7 KiB)  TX bytes:4817 (4.7 KiB)

ppp0      Link encap:Point-to-Point Protocol
      inet addr:89.1.203.31  P-t-P:212.29.206.60  Mask:255.255.255.255
      UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
      RX packets:269808 errors:0 dropped:0 overruns:0 frame:0
      TX packets:249776 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:3
      RX bytes:269452852 (256.9 MiB)  TX bytes:15987305 (15.2 MiB)

sit0      Link encap:IPv6-in-IPv4
      inet6 addr: ::89.1.203.31/96 Диапазон:Compat
      inet6 addr: ::127.0.0.1/96 Диапазон:Unknown
      UP RUNNING NOARP  MTU:1480  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

sit1      Link encap:IPv6-in-IPv4
      inet6 addr: 2001:618:400::591:cb1f/128 Диапазон:Общий
      inet6 addr: fe80::5901:cb1f/64 Диапазон:Link
      UP POINTOPOINT RUNNING NOARP  MTU:1472  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:0 (0.0 b)  TX bytes:588 (588.0 b)




any ideas how to solve that problem?

i tryed editing the script and changing all eth1 to eth0 because in ifconfig i dont see any eth1 connection but i got error too



Code:
snake@delta:~$ sudo sh LinuxScript.sh
SIOCSIFADDR: File exists
IPv6 configuration failed!




thanks.

]]> <![CDATA[How I Got Bind9 Working On Debian Etch]]> https://www.linux-noob.com/forums/thread-1483.html Tue, 27 Mar 2007 18:48:36 +0200 DustyBin]]> https://www.linux-noob.com/forums/thread-1483.html TARGET MACHINE

 

apt-get install bind9

 

edit /etc/bind/named.conf.local



Code:
zone "yourdomain.net" {
    type master;
    file "/etc/bind/zones/yourdomain.net.db";
    };

zone "0.168.192.in-addr.arpa" {
type master;
file "/etc/bind/zones/rev.0.168.192.in-addr.arpa";
};




 

mkdir /etc/bind/zones

edit /etc/bind/zones/yourdomain.net.db



Code:
yourdomain.net.      IN      SOA     ns1.yourdomain.net. admin.yourdomain.net. (
                                                    0000000001
                                                    28800
                                                    3600
                                                    604800
                                                    38400
)

yourdomain.net.      IN      NS              ns1.yourdomain.net.
yourdomain.net.      IN      MX     10       yourdomain.net.

www              IN      A       **serverIP**
mta              IN      A       **serverIP**
ns1              IN      A       **serverIP**




 

edit /etc/bind/zones/rev.0.168.192.in-addr.arpa

The number before IN PTR yourdomain.net. is the machine address of the DNS server. in my case, it's 3, as my IP address is 192.168.0.3.



Code:
@ IN SOA ns1.yourdomain.net. admin.yourdomain.net. (
                    0000000001;
                    28800;
                    604800;
                    604800;
                    86400
)

                 IN    NS     ns1.yourdomain.net.
3                    IN    PTR    yourdomain.net.




 

CONFIGURING THE NETWORK INTERFACES

 

edit etc/network/interfaces

my particular LAN has static local addresses assigned by my router. I removed anything to do with DHCP so it wont overwrite /etc/resolv.conf and entered the relevant details so it looked like this but remember to change your details accordingly for your setup.



Code:
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
auto eth0
iface eth0 inet static
address 192.168.0.2
gateway 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255




 

Remove network-manager so this also doesnt overwrite the /etc/resolv.conf

 

apt-get remove --purge network-manager

 

edit /etc/resolv.conf



Code:
nameserver 127.0.0.1




 

Restart the network interfaces and check to make sure /etc/resolv.conf hasnt changed!

 

/etc/init.d/networking restart

 

 

now try pinging www.yourdomain.net

 

If all went well you could repeat 'CONFIGURING THE NETWORK INTERFACES' for other machines on your LAN so it uses bind9 as the name server but remember to point /etc/resolv.conf at the machine running bind9!

 

 

CHROOTING BIND9

 

It is VERY IMPORTANT to be running Bind9 as secure as possible. Heres how you chroot Bind9 on Debian Etch.

magikman from #linux-noob / efnet kindly showed me how to do this.

 

edit /etc/default/bind9



Code:
OPTIONS="-u bind -t /var/lib/named"




mkdir -p /var/lib/named/etc

mkdir /var/lib/named/dev

mkdir -p /var/lib/named/var/cache/bind

mkdir -p /var/lib/named/var/run/bind/run

mv /etc/bind /var/lib/named/etc

ln -s /var/lib/named/etc/bind /etc/bind

mknod /var/lib/named/dev/null c 1 3

mknod /var/lib/named/dev/random c 1 8

chmod 666 /var/lib/named/dev/null /var/lib/named/dev/random

chown -R bind:bind /var/lib/named/var/*

chown -R bind:bind /var/lib/named/etc/bind

 

edit /etc/init.d/sysklogd



Code:
SYSLOGD="-a /var/lib/named/dev/log"




/etc/init.d/sysklogd restart

 

/etc/init.d/bind9 restart

 

Now you will running Bind9 chrooted :-)

]]> TARGET MACHINE

 

apt-get install bind9

 

edit /etc/bind/named.conf.local



Code:
zone "yourdomain.net" {
    type master;
    file "/etc/bind/zones/yourdomain.net.db";
    };

zone "0.168.192.in-addr.arpa" {
type master;
file "/etc/bind/zones/rev.0.168.192.in-addr.arpa";
};




 

mkdir /etc/bind/zones

edit /etc/bind/zones/yourdomain.net.db



Code:
yourdomain.net.      IN      SOA     ns1.yourdomain.net. admin.yourdomain.net. (
                                                    0000000001
                                                    28800
                                                    3600
                                                    604800
                                                    38400
)

yourdomain.net.      IN      NS              ns1.yourdomain.net.
yourdomain.net.      IN      MX     10       yourdomain.net.

www              IN      A       **serverIP**
mta              IN      A       **serverIP**
ns1              IN      A       **serverIP**




 

edit /etc/bind/zones/rev.0.168.192.in-addr.arpa

The number before IN PTR yourdomain.net. is the machine address of the DNS server. in my case, it's 3, as my IP address is 192.168.0.3.



Code:
@ IN SOA ns1.yourdomain.net. admin.yourdomain.net. (
                    0000000001;
                    28800;
                    604800;
                    604800;
                    86400
)

                 IN    NS     ns1.yourdomain.net.
3                    IN    PTR    yourdomain.net.




 

CONFIGURING THE NETWORK INTERFACES

 

edit etc/network/interfaces

my particular LAN has static local addresses assigned by my router. I removed anything to do with DHCP so it wont overwrite /etc/resolv.conf and entered the relevant details so it looked like this but remember to change your details accordingly for your setup.



Code:
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
auto eth0
iface eth0 inet static
address 192.168.0.2
gateway 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255




 

Remove network-manager so this also doesnt overwrite the /etc/resolv.conf

 

apt-get remove --purge network-manager

 

edit /etc/resolv.conf



Code:
nameserver 127.0.0.1




 

Restart the network interfaces and check to make sure /etc/resolv.conf hasnt changed!

 

/etc/init.d/networking restart

 

 

now try pinging www.yourdomain.net

 

If all went well you could repeat 'CONFIGURING THE NETWORK INTERFACES' for other machines on your LAN so it uses bind9 as the name server but remember to point /etc/resolv.conf at the machine running bind9!

 

 

CHROOTING BIND9

 

It is VERY IMPORTANT to be running Bind9 as secure as possible. Heres how you chroot Bind9 on Debian Etch.

magikman from #linux-noob / efnet kindly showed me how to do this.

 

edit /etc/default/bind9



Code:
OPTIONS="-u bind -t /var/lib/named"




mkdir -p /var/lib/named/etc

mkdir /var/lib/named/dev

mkdir -p /var/lib/named/var/cache/bind

mkdir -p /var/lib/named/var/run/bind/run

mv /etc/bind /var/lib/named/etc

ln -s /var/lib/named/etc/bind /etc/bind

mknod /var/lib/named/dev/null c 1 3

mknod /var/lib/named/dev/random c 1 8

chmod 666 /var/lib/named/dev/null /var/lib/named/dev/random

chown -R bind:bind /var/lib/named/var/*

chown -R bind:bind /var/lib/named/etc/bind

 

edit /etc/init.d/sysklogd



Code:
SYSLOGD="-a /var/lib/named/dev/log"




/etc/init.d/sysklogd restart

 

/etc/init.d/bind9 restart

 

Now you will running Bind9 chrooted :-)

]]> <![CDATA[BIND9 Configuration Guidance]]> https://www.linux-noob.com/forums/thread-1498.html Sat, 24 Mar 2007 15:40:59 +0100 magikman]]> https://www.linux-noob.com/forums/thread-1498.html I am currently setting up a DNS server for several domains that i own and i would like some input from you all on my configuration options, etc. The domains have been replaced by example.com example1.com and example2.com.

 

Okay, first my options file:



Code:
options {
    directory "/etc/bind";
    allow-query { localhost; };
    allow-recursion { 127.0.0.1; };
    listen-on { <IP of Server>; };
    allow-transfer { none; };
    auth-nxdomain yes;

};




 

named.conf:



Code:
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
    type hint;
    file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
    type master;
    file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
    type master;
    file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
    type master;
    file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
    type master;
    file "/etc/bind/db.255";
};

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
//  Because many of our users are uncomfortable receiving undelegated answers
//  from root or top level domains, other than a few for whom that behaviour
//  has been trusted and expected for quite some length of time, we have now
//  introduced the "root-delegations-only" feature which applies delegation-only
//  logic to all top level domains, and to the root domain.  An exception list
//  should be specified, including "MUSEUM" and "DE", and any other top level
//  domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

include "/etc/bind/named.conf.local";




 

named.conf.local:



Code:
zone "example.com" {
    type master;
    file "example.com";
    notify no;
};

zone "example1.com" {
    type master;
    file "example1.com";
    notify no;
};

zone "example2.com" {
    type master;
    file "example2.com";
    notify no;
};




 

example.com



Code:
@       IN      SOA     example.com.    root.example.com. (
                            2007032401
                            28800
                            86400    
                            2419200
                            604800 )

    IN      NS      ns1.example.com.
    IN      MX      10      mail.example.com.

ns1.example.com         IN      A       <IP of server>




 

example1.com



Code:
@       IN      SOA     www.example1.com.     root.example1.com. (
                            2007032001; Serial
                            604800    ; Refresh
                            86400        ; Retry
                            2419200; Expire
                            604800 )     ; Default TTL

    IN      NS      ns1.example.com.
    IN      MX      10      mail.example.com.

ns1.example.com         IN      A       <IP of server>




 

example2.com



Code:
@       IN      SOA     www.example2.com. root.example2.com. (
                            2007032001; Serial
                            604800    ; Refresh
                            86400        ; Retry
                            2419200; Expire
                            604800 )     ; Default TTL

    IN      NS      ns1.example.com.
    IN      MX      10      mail.example.com.

ns1.example.com         IN      A       <IP of server>




 

As you can see the dns server will be authoritative for all three domains. I am also going to be putting up a mail server in the near future and would like to serve mail for all three domains from the one server (mail.example.com). If there is anything wrong with these definitions, or if there is something that can be done better, please let me know. Smile

]]> I am currently setting up a DNS server for several domains that i own and i would like some input from you all on my configuration options, etc. The domains have been replaced by example.com example1.com and example2.com.

 

Okay, first my options file:



Code:
options {
    directory "/etc/bind";
    allow-query { localhost; };
    allow-recursion { 127.0.0.1; };
    listen-on { <IP of Server>; };
    allow-transfer { none; };
    auth-nxdomain yes;

};




 

named.conf:



Code:
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
    type hint;
    file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
    type master;
    file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
    type master;
    file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
    type master;
    file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
    type master;
    file "/etc/bind/db.255";
};

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
//  Because many of our users are uncomfortable receiving undelegated answers
//  from root or top level domains, other than a few for whom that behaviour
//  has been trusted and expected for quite some length of time, we have now
//  introduced the "root-delegations-only" feature which applies delegation-only
//  logic to all top level domains, and to the root domain.  An exception list
//  should be specified, including "MUSEUM" and "DE", and any other top level
//  domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

include "/etc/bind/named.conf.local";




 

named.conf.local:



Code:
zone "example.com" {
    type master;
    file "example.com";
    notify no;
};

zone "example1.com" {
    type master;
    file "example1.com";
    notify no;
};

zone "example2.com" {
    type master;
    file "example2.com";
    notify no;
};




 

example.com



Code:
@       IN      SOA     example.com.    root.example.com. (
                            2007032401
                            28800
                            86400    
                            2419200
                            604800 )

    IN      NS      ns1.example.com.
    IN      MX      10      mail.example.com.

ns1.example.com         IN      A       <IP of server>




 

example1.com



Code:
@       IN      SOA     www.example1.com.     root.example1.com. (
                            2007032001; Serial
                            604800    ; Refresh
                            86400        ; Retry
                            2419200; Expire
                            604800 )     ; Default TTL

    IN      NS      ns1.example.com.
    IN      MX      10      mail.example.com.

ns1.example.com         IN      A       <IP of server>




 

example2.com



Code:
@       IN      SOA     www.example2.com. root.example2.com. (
                            2007032001; Serial
                            604800    ; Refresh
                            86400        ; Retry
                            2419200; Expire
                            604800 )     ; Default TTL

    IN      NS      ns1.example.com.
    IN      MX      10      mail.example.com.

ns1.example.com         IN      A       <IP of server>




 

As you can see the dns server will be authoritative for all three domains. I am also going to be putting up a mail server in the near future and would like to serve mail for all three domains from the one server (mail.example.com). If there is anything wrong with these definitions, or if there is something that can be done better, please let me know. Smile

]]> <![CDATA[Dynamic DNS : Update query]]> https://www.linux-noob.com/forums/thread-1534.html Wed, 14 Mar 2007 12:08:59 +0100 nsvora]]> https://www.linux-noob.com/forums/thread-1534.html Hi,

I am using BIND 9.2.4 on LINUX 2.6.9. I am facing the following issue:

The domain name is set to testdns.com and when i update my host name as test, the update goes through fine to the DDNS server.

But when my host name reaches 64 characters, the server sends the "Format Error" response code.

I know domain name can be upto 256 bytes, but is 63 limiting factor for the host name?

 

Any help is appreciated.

 

Thanks in advance,

nsvora

]]> Hi,

I am using BIND 9.2.4 on LINUX 2.6.9. I am facing the following issue:

The domain name is set to testdns.com and when i update my host name as test, the update goes through fine to the DDNS server.

But when my host name reaches 64 characters, the server sends the "Format Error" response code.

I know domain name can be upto 256 bytes, but is 63 limiting factor for the host name?

 

Any help is appreciated.

 

Thanks in advance,

nsvora

]]> <![CDATA[Dynamic DNS with static IP]]> https://www.linux-noob.com/forums/thread-1698.html Fri, 08 Dec 2006 22:47:38 +0100 nsvora]]> https://www.linux-noob.com/forums/thread-1698.html Hi All,

I have a Linux machine having static IP configuration ( without DHCP). And if this configuration is changed, should this information be updated in the DNS server?

 

In short, does Dynamic DNS make sense with static IP configuration?

 

Any comment in this regard is highly appreciated.

 

With Regards,

nsv

]]> Hi All,

I have a Linux machine having static IP configuration ( without DHCP). And if this configuration is changed, should this information be updated in the DNS server?

 

In short, does Dynamic DNS make sense with static IP configuration?

 

Any comment in this regard is highly appreciated.

 

With Regards,

nsv

]]> <![CDATA[Vhost on irc]]> https://www.linux-noob.com/forums/thread-1733.html Thu, 09 Nov 2006 20:57:01 +0100 Star]]> https://www.linux-noob.com/forums/thread-1733.html Okey .. so .. i`ve done a lot of things on linux .. and i know what i`m intrested about .. but now i have something else that i`m intrested .. and i really can`t find any solid documentation how to do it ..

 

so .. i have my own linux machine with slack 10.2 ( static ip ofcourse ) & my own domain .

The domain`s nameserver is on my linux machine so everything is okay so far.

 

Besides everything else that i run on the slack , i have a psybnc.

I want to set up a vhost ( on my domain ) .. so when I connect to a irc network , the name of the domain is shown , not the ip.

 

I've read about Reverse DNS , but i really can`t get it ...

 

So ... by any change .. can somebody explain to me .. step by step .. what i have to do ?

 

Thanks very much & waiting for an answer.

]]> Okey .. so .. i`ve done a lot of things on linux .. and i know what i`m intrested about .. but now i have something else that i`m intrested .. and i really can`t find any solid documentation how to do it ..

 

so .. i have my own linux machine with slack 10.2 ( static ip ofcourse ) & my own domain .

The domain`s nameserver is on my linux machine so everything is okay so far.

 

Besides everything else that i run on the slack , i have a psybnc.

I want to set up a vhost ( on my domain ) .. so when I connect to a irc network , the name of the domain is shown , not the ip.

 

I've read about Reverse DNS , but i really can`t get it ...

 

So ... by any change .. can somebody explain to me .. step by step .. what i have to do ?

 

Thanks very much & waiting for an answer.

]]> <![CDATA[Dynamic DNS Issue]]> https://www.linux-noob.com/forums/thread-1752.html Thu, 26 Oct 2006 04:29:44 +0200 nsvora]]> https://www.linux-noob.com/forums/thread-1752.html Hi All,

 

While testing the DDNS server configuration with proprietory DHCP and DDNS client, I noticed a strange thing. Any help here is appreciated.

 

Pre-condition:

----------------

DHCP and DDNS server are running on a single LINUX machine having following version:

Linux ns1.testdns.com 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 2006 i686 i686 i386 GNU/Linux

 

The DHCP server was able to generate the dynamic IP Address as specified in the dhcpd.conf.

DDNS server was able to add the entries in the forward and reverse zone files eg : testdns.com and 1.168.192.in-addr.arpa

This ensures that DHCP and DDNS server settings are correct.

 

Test Condition:

---------------

I modified the client host name and restarted the named service so that changes are reflected in the zone files. The forward zone file was expected to be updated with the modified host name.

 

Results:

----------

Forward zone had two entries viz; one with old host name and other with new host name.

 

Analysis:

------------

I have found that this is happening because in DDNS client code,

before updating the server database with modified host name, we are checking whether a record with

]]> Hi All,

 

While testing the DDNS server configuration with proprietory DHCP and DDNS client, I noticed a strange thing. Any help here is appreciated.

 

Pre-condition:

----------------

DHCP and DDNS server are running on a single LINUX machine having following version:

Linux ns1.testdns.com 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 2006 i686 i686 i386 GNU/Linux

 

The DHCP server was able to generate the dynamic IP Address as specified in the dhcpd.conf.

DDNS server was able to add the entries in the forward and reverse zone files eg : testdns.com and 1.168.192.in-addr.arpa

This ensures that DHCP and DDNS server settings are correct.

 

Test Condition:

---------------

I modified the client host name and restarted the named service so that changes are reflected in the zone files. The forward zone file was expected to be updated with the modified host name.

 

Results:

----------

Forward zone had two entries viz; one with old host name and other with new host name.

 

Analysis:

------------

I have found that this is happening because in DDNS client code,

before updating the server database with modified host name, we are checking whether a record with

]]> <![CDATA[strange reverse dns issue]]> https://www.linux-noob.com/forums/thread-2082.html Sat, 18 Mar 2006 01:10:49 +0100 wizzard]]> https://www.linux-noob.com/forums/thread-2082.html making a traceroute from Level3 network

 

Show Level 3 (Frankfurt, Germany) Traceroute to 81.196.170.68

 

1 ge-1-1-51.car1.Frankfurt1.Level3.net (4.68.118.15) 0 msec

ge-1-2-56.car1.Frankfurt1.Level3.net (4.68.118.175) 0 msec

ge-1-1-55.car1.Frankfurt1.Level3.net (4.68.118.143) 0 msec

2 212.162.44.38 0 msec 4 msec

frankfurt2-cr2.ge3-0.rdsnet.ro (62.67.36.182) 0 msec

3 213.157.172.66 [AS8708 {RIPE-ASNBLOCK7}] 24 msec 24 msec 24 msec

4 81-196-170-68.rdsnet.ro (81.196.170.68) [AS8708 {RIPE-ASNBLOCK7}] 24 msec 36 msec 24 msec

 

 

and same traceroute from telia network

 

1 kbn-b2-geth15-0-11.telia.net (213.248.66.73) [AS 1299] 0 msec 0 msec 0 msec

2 kbn-bb2-pos1-0-0.telia.net (213.248.65.13) [AS 1299] 0 msec 0 msec 0 msec

3 s-bb2-link.telia.net (213.248.65.165) [AS 1299] 12 msec 12 msec 16 msec

4 s-b3-pos4-0.telia.net (213.248.66.10) [AS 1299] 12 msec 12 msec 12 msec

5 ge-6-14.car2.Stockholm1.Level3.net (4.68.111.245) [AS 3356] 16 msec 12 msec 16 msec

6 ge-0-0-0.mp2.Stockholm1.Level3.net (4.68.96.225) [AS 3356] 16 msec 16 msec 200 msec

7 as-1-0.bbr2.Frankfurt1.Level3.net (212.187.128.97) [AS 3356] 32 msec 28 msec 28 msec

8 ge-1-2-54.car1.Frankfurt1.Level3.net (4.68.118.111) [AS 3356] 32 msec

ge-1-2-56.car1.Frankfurt1.Level3.net (4.68.118.175) [AS 3356] 28 msec

ge-1-1-51.car1.Frankfurt1.Level3.net (4.68.118.15) [AS 3356] 32 msec

9 frankfurt2-cr2.ge3-0.rdsnet.ro (62.67.36.182) [AS 3356] 28 msec 28 msec

212.162.44.38 [AS 3356] 32 msec

10 213.157.172.66 [AS 8708] 48 msec 52 msec 52 msec

11 headend.sm.rdsnet.ro (81.196.170.68) [AS 8708] 52 msec 52 msec 52 msec

 

so why in telia network the revers dns of my host is resolved and from level3 not ?

 

and exemples cand go further.

 

whereis the problem ?

]]> making a traceroute from Level3 network

 

Show Level 3 (Frankfurt, Germany) Traceroute to 81.196.170.68

 

1 ge-1-1-51.car1.Frankfurt1.Level3.net (4.68.118.15) 0 msec

ge-1-2-56.car1.Frankfurt1.Level3.net (4.68.118.175) 0 msec

ge-1-1-55.car1.Frankfurt1.Level3.net (4.68.118.143) 0 msec

2 212.162.44.38 0 msec 4 msec

frankfurt2-cr2.ge3-0.rdsnet.ro (62.67.36.182) 0 msec

3 213.157.172.66 [AS8708 {RIPE-ASNBLOCK7}] 24 msec 24 msec 24 msec

4 81-196-170-68.rdsnet.ro (81.196.170.68) [AS8708 {RIPE-ASNBLOCK7}] 24 msec 36 msec 24 msec

 

 

and same traceroute from telia network

 

1 kbn-b2-geth15-0-11.telia.net (213.248.66.73) [AS 1299] 0 msec 0 msec 0 msec

2 kbn-bb2-pos1-0-0.telia.net (213.248.65.13) [AS 1299] 0 msec 0 msec 0 msec

3 s-bb2-link.telia.net (213.248.65.165) [AS 1299] 12 msec 12 msec 16 msec

4 s-b3-pos4-0.telia.net (213.248.66.10) [AS 1299] 12 msec 12 msec 12 msec

5 ge-6-14.car2.Stockholm1.Level3.net (4.68.111.245) [AS 3356] 16 msec 12 msec 16 msec

6 ge-0-0-0.mp2.Stockholm1.Level3.net (4.68.96.225) [AS 3356] 16 msec 16 msec 200 msec

7 as-1-0.bbr2.Frankfurt1.Level3.net (212.187.128.97) [AS 3356] 32 msec 28 msec 28 msec

8 ge-1-2-54.car1.Frankfurt1.Level3.net (4.68.118.111) [AS 3356] 32 msec

ge-1-2-56.car1.Frankfurt1.Level3.net (4.68.118.175) [AS 3356] 28 msec

ge-1-1-51.car1.Frankfurt1.Level3.net (4.68.118.15) [AS 3356] 32 msec

9 frankfurt2-cr2.ge3-0.rdsnet.ro (62.67.36.182) [AS 3356] 28 msec 28 msec

212.162.44.38 [AS 3356] 32 msec

10 213.157.172.66 [AS 8708] 48 msec 52 msec 52 msec

11 headend.sm.rdsnet.ro (81.196.170.68) [AS 8708] 52 msec 52 msec 52 msec

 

so why in telia network the revers dns of my host is resolved and from level3 not ?

 

and exemples cand go further.

 

whereis the problem ?

]]> <![CDATA[Bind9 ACLs]]> https://www.linux-noob.com/forums/thread-2361.html Fri, 28 Oct 2005 03:05:45 +0200 cyris]]> https://www.linux-noob.com/forums/thread-2361.html I'm trying to setup Bind9 so that people cant point their dns server addresses to my box and do lookups off my server, but still have them able to query my dns server for the domains its authoritive for.

 

My named.conf

 

acl bogusnets {0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3; 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16;};

options {

directory "/var/named";

version "Tongue";

blackhole { bogusnets; };

allow-recursion { none; };

};

zone "xyz.ca" {

type master;

file "data/named.xyz.ca";

allow-query { any; };

};

 

The only way I've been able to stop people from doing lookups off my server is by setting recursion to none. I would like to have my localnet to have the option of doing lookups off my box so I need a more suited way of controling who does lookups off my box.

 

I have read about views and I wont be serving different content to my localnet so I dont think I require them.

 

Version info

 

bind-utils-9.3.1-4

bind-chroot-9.3.1-4

bind-libs-9.3.1-4

ypbind-1.17.2-5

 

2.6.11-1.1369_FC4

 

Thanks

]]> I'm trying to setup Bind9 so that people cant point their dns server addresses to my box and do lookups off my server, but still have them able to query my dns server for the domains its authoritive for.

 

My named.conf

 

acl bogusnets {0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3; 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16;};

options {

directory "/var/named";

version "Tongue";

blackhole { bogusnets; };

allow-recursion { none; };

};

zone "xyz.ca" {

type master;

file "data/named.xyz.ca";

allow-query { any; };

};

 

The only way I've been able to stop people from doing lookups off my server is by setting recursion to none. I would like to have my localnet to have the option of doing lookups off my box so I need a more suited way of controling who does lookups off my box.

 

I have read about views and I wont be serving different content to my localnet so I dont think I require them.

 

Version info

 

bind-utils-9.3.1-4

bind-chroot-9.3.1-4

bind-libs-9.3.1-4

ypbind-1.17.2-5

 

2.6.11-1.1369_FC4

 

Thanks

]]> <![CDATA[Reverse DNS]]> https://www.linux-noob.com/forums/thread-2384.html Mon, 10 Oct 2005 09:24:33 +0200 Webbie]]> https://www.linux-noob.com/forums/thread-2384.html Hey guyz, alright, i had my reverse dns working for awhile now, then all the sudden something happend to my zone files, so i had to remake them, now when i redid my reverse.zone file and added the PTR records im getting this from bind when i restart the services

 

Oct 10 00:19:02 web named[14032]: zone 177.39.65.in-addr.arpa/IN: loading master file /var/named/reverse.zone.db: unexpected end of input

Oct 10 00:19:02 web named[14032]: dns_rdata_fromtext: /var/named/reverse.zone.db:8: near eol: unexpected end of input

Oct 10 00:19:02 web named[14032]: zone reverse.zone/IN: loading master file /var/named/reverse.zone.db: unexpected end of input

 

 

 

ive been at this for hrs now, cant seem to fix it

]]> Hey guyz, alright, i had my reverse dns working for awhile now, then all the sudden something happend to my zone files, so i had to remake them, now when i redid my reverse.zone file and added the PTR records im getting this from bind when i restart the services

 

Oct 10 00:19:02 web named[14032]: zone 177.39.65.in-addr.arpa/IN: loading master file /var/named/reverse.zone.db: unexpected end of input

Oct 10 00:19:02 web named[14032]: dns_rdata_fromtext: /var/named/reverse.zone.db:8: near eol: unexpected end of input

Oct 10 00:19:02 web named[14032]: zone reverse.zone/IN: loading master file /var/named/reverse.zone.db: unexpected end of input

 

 

 

ive been at this for hrs now, cant seem to fix it

]]> <![CDATA[DNS configuration]]> https://www.linux-noob.com/forums/thread-2434.html Mon, 12 Sep 2005 00:09:33 +0200 wizzard]]> https://www.linux-noob.com/forums/thread-2434.html i use afraid.org to make an alias to my ip adress and i set at home at dns usig the tutorial from this forum and i have some problems

 

i have wiz.rdstel.org that point to my ip 82.79.48.111

and i want www.wiz.rdstel.org and ftp.wiz.rdstel.org to do like same but i have a problem from my internal netwok and from server i can ping www.wiz.rdstel.org and ftp.wiz.rdstel.org but from the internet i can't

 

i open 53 port but still not working can some one help me ?

]]> i use afraid.org to make an alias to my ip adress and i set at home at dns usig the tutorial from this forum and i have some problems

 

i have wiz.rdstel.org that point to my ip 82.79.48.111

and i want www.wiz.rdstel.org and ftp.wiz.rdstel.org to do like same but i have a problem from my internal netwok and from server i can ping www.wiz.rdstel.org and ftp.wiz.rdstel.org but from the internet i can't

 

i open 53 port but still not working can some one help me ?

]]>