About this list Date view Thread view Subject view Author view Attachment view

From: Justin M Kuntz (jkuntz_at_prominic.com)
Date: Thu 05 Dec 2002 - 21:57:40 GMT


Hello,

We've got a bit of a problem. We're using vservers but trying to get
named/bind working outside of the vservers in this case and we're having
trouble doing even that. I know this has been discussed on this list
before, but I don't have a way to search the only archive at
http://www.paul.sladen.org/vserver/archives/

Our goal is to simply have named responding on 172.17.19.1 port 53 UDP.

Please let us know if you have any ideas, as we need to get this working
urgently. Thank you!

version of bind:
bind-9.2.0-8

kernel version:
2.4.19ctx-13

header of named.conf (located in /var/named/internal/named.conf ):

options {
  directory "/var/named/internal";
  listen-on port 53 { 172.17.20.17;172.17.19.1; };
  pid-file "/var/run/named-int.pid";
};

logging {
  category default { default_syslog; default_debug; };
};

zone "." {
  type hint;
  file "/var/named/named.ca";
};

zone "0.0.127.in-addr.arpa" {
  type master;
  file "/var/named/named.local";
};

bind is started using:
/usr/sbin/named -c /var/named/internal/named.conf

messages bind is outputting to /var/log/messages (and we are wondering
about the bolded messages):
Dec 5 21:29:23 linux-16 named[9550]: starting BIND 9.2.0 -c
/var/named/internal/named.conf
Dec 5 21:29:23 linux-16 named[9550]: using 2 CPUs
Dec 5 21:29:23 linux-16 named[9552]: loading configuration from
'/var/named/internal/named.conf'
Dec 5 21:29:23 linux-16 named[9552]: no IPv6 interfaces found
Dec 5 21:29:23 linux-16 named[9552]: listening on IPv4 interface eth0,
172.17.20.17#53
>> Dec 5 21:29:23 linux-16 named[9552]: listening on IPv4 interface
eth0:1, 172.17.19.1#53
>> Dec 5 21:29:23 linux-16 named[9552]: could not listen on UDP socket:
address not available
Dec 5 21:29:23 linux-16 named[9552]: creating IPv4 interface eth0:1
failed; interface ignored
Dec 5 21:29:23 linux-16 named[9552]: command channel listening on
127.0.0.1#953

ifconfig output:
th0 Link encap:Ethernet HWaddr 00:01:02:C9:1F:FC
          inet addr:172.17.20.17 Bcast:172.17.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:8745991 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7719170 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:3487008494 (3325.4 Mb) TX bytes:1106238875 (1054.9 Mb)
          Interrupt:5 Base address:0xe400

eth0:00B4 Link encap:Ethernet HWaddr 00:01:02:C9:1F:FC
          inet addr:172.17.1.40 Bcast:172.17.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:5 Base address:0xe400

eth0:00B5 Link encap:Ethernet HWaddr 00:01:02:C9:1F:FC
          inet addr:172.17.1.41 Bcast:172.17.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:5 Base address:0xe400

eth0:00B6 Link encap:Ethernet HWaddr 00:01:02:C9:1F:FC
          inet addr:172.17.1.42 Bcast:172.17.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:5 Base address:0xe400

eth0:1 Link encap:Ethernet HWaddr 00:01:02:C9:1F:FC
          inet addr:172.17.19.1 Bcast:172.17.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:5 Base address:0xe400

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:738809 errors:0 dropped:0 overruns:0 frame:0
          TX packets:738809 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:93669454 (89.3 Mb) TX bytes:93669454 (89.3 Mb)


About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Fri 13 Dec 2002 - 03:49:14 GMT by hypermail 2.1.3