Post here if you are a new Porteus member and you're looking for some help.
-
inukaze
- Black ninja
- Posts: 47
- Joined: 06 Jul 2023, 07:40
- Distribution: Slackware
Post#1
by inukaze » 15 Aug 2023, 16:59
Hi there, i had download this files :
libuv ->
http://ftp.osuosl.org/pub/slackware/sla ... 6_64-1.txz
bind ->
http://ftp.osuosl.org/pub/slackware/sla ... ck15.0.txz
i convert to xzm modules. first i load libuv because the rndc looks for file libuv.so.1 to work
second i load bind module
I do the follow on terminal like root
Code: Select all
rndc status
rndc: neither /etc/rndc.conf nor /etc/rndc.key was found
/etc/rc.d/rc.bind
bash: /etc/rc.d/rc.bind: Permiso denegado
chmod +x /etc/rc.d/rc.bind
/etc/rc.d/rc.bind start
chown: usuario inválido: «named:named»
chown: usuario inválido: «named:named»
Starting BIND: /usr/sbin/named -u named
named: user 'named' unknown
well i need create group and user called «named» but i don't remember which are the defaults properties for slackware of that group and user
the another thing i don't remember how i generate the file /etc/rndc.key on my Slackware64 14.2, but the file exist i dont have /etc/rndc.conf
i just use rndc for flush dns cache.
Someone can tell me how i should create the user and group named default for Slackware64 15.0 ?
Last edited by
inukaze on 16 Aug 2023, 13:17, edited 1 time in total.
inukaze
-
beny
- Full of knowledge
- Posts: 2098
- Joined: 02 Jan 2011, 11:33
- Location: italy
Post#2
by beny » 15 Aug 2023, 18:01
bash-5.2# sh '/etc/rc.d/rc.bind' start
Starting BIND: /usr/sbin/named -u named
bash-5.2# bind --help
bind: usage: bind [-lpsvPSVX] [-m keymap] [-f filename] [-q name] [-u name] [-r keyseq] [-x keyseq:shell-command] [keyseq:readline-function or readline-command]
bash-5.2# rndc
Usage: rndc [-b address] [-c config] [-s server] [-p port]
[-k key-file ] [-y key] [-r] [-V] [-4 | -6] command
bash-5.2# rndc status
version: BIND 9.18.17 (Extended Support Version) <id:42ca761>
running on localhost: Linux x86_64 6.1.5-beny #1 SMP Fri Jan 13 20:25:03 CET 2023
boot time: Tue, 15 Aug 2023 17:52:03 GMT
last configured: Tue, 15 Aug 2023 17:52:03 GMT
configuration file: /etc/named.conf
CPUs found: 6
worker threads: 6
UDP listeners per interface: 6
number of zones: 102 (99 automatic)
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/900/1000
tcp clients: 0/150
TCP high-water: 0
server is up and running
bash-5.2#
hi, i think you don't need user: named, but all the net software need root privilege to run,take a look at /etc/named.conf
beny
-
inukaze
- Black ninja
- Posts: 47
- Joined: 06 Jul 2023, 07:40
- Distribution: Slackware
Post#3
by inukaze » 15 Aug 2023, 18:18
Code: Select all
guest@Porteus:~$ su
Contraseña:
root@Porteus:/home/guest# cat /etc/named.conf
options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
//
// a caching only nameserver config
//
zone "." IN {
type hint;
file "caching-example/named.root";
};
zone "localhost" IN {
type master;
file "caching-example/localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "caching-example/named.local";
allow-update { none; };
};
root@Porteus:/home/guest# /etc/rc.d/rc.bind start
chown: usuario inválido: «named:named»
chown: usuario inválido: «named:named»
Starting BIND: /usr/sbin/named -u named
named: user 'named' unknown
inukaze
-
beny
- Full of knowledge
- Posts: 2098
- Joined: 02 Jan 2011, 11:33
- Location: italy
Post#4
by beny » 15 Aug 2023, 18:37
hi also with sh /etc/rc.d/rc.bind start, is a script you need the sh all the rc.d start with it,i am on a slackware now but is the same as porteus..
beny
-
inukaze
- Black ninja
- Posts: 47
- Joined: 06 Jul 2023, 07:40
- Distribution: Slackware
Post#5
by inukaze » 15 Aug 2023, 18:43
beny wrote: ↑15 Aug 2023, 18:37
sh /etc/rc.d/rc.bind start
Code: Select all
sh /etc/rc.d/rc.bind start
chown: usuario inválido: «named:named»
chown: usuario inválido: «named:named»
Starting BIND: /usr/sbin/named -u named
named: user 'named' unknown
inukaze
-
beny
- Full of knowledge
- Posts: 2098
- Joined: 02 Jan 2011, 11:33
- Location: italy
Post#6
by beny » 15 Aug 2023, 20:30
hi ,you are right, seem porteus do not start bind but slackware can do it
beny
-
inukaze
- Black ninja
- Posts: 47
- Joined: 06 Jul 2023, 07:40
- Distribution: Slackware
Post#7
by inukaze » 15 Aug 2023, 22:20
# Start of rndc.conf
key "rndc-key" {
algorithm hmac-sha256;
secret "L07C/+KOLiXa3mJw88rqrUuxxU+waSp02fshGtHuAmQ=";
};
options {
default-key "rndc-key";
default-server 127.0.0.1;
default-port 953;
};
# End of rndc.conf
# Use with the following in named.conf, adjusting the allow list as needed:
# key "rndc-key" {
# algorithm hmac-sha256;
# secret "L07C/+KOLiXa3mJw88rqrUuxxU+waSp02fshGtHuAmQ=";
# };
#
# controls {
# inet 127.0.0.1 port 953
# allow { 127.0.0.1; } keys { "rndc-key"; };
# };
# End of named.conf
rndc: neither /etc/rndc.conf nor /etc/rndc.key was found
Code: Select all
echo 'key "rndc-key" {
algorithm hmac-sha256;
secret "L07C/+KOLiXa3mJw88rqrUuxxU+waSp02fshGtHuAmQ=";
};' | tee /etc/rndc.key
key "rndc-key" {
algorithm hmac-sha256;
secret "L07C/+KOLiXa3mJw88rqrUuxxU+waSp02fshGtHuAmQ=";
};
rndc: connect failed: 127.0.0.1#953: connection refused
Well i go try the last idea i had :
version: BIND 9.16.42 (Extended Support Version) <id:a62d1bd>
running on Porteus: Linux x86_64 5.18.8-porteus #1 SMP PREEMPT_DYNAMIC Sat Jul 2 10:05:31 MSK 2022
boot time: Tue, 15 Aug 2023 22:18:55 GMT
last configured: Tue, 15 Aug 2023 22:18:55 GMT
configuration file: /etc/named.conf
CPUs found: 2
worker threads: 2
UDP listeners per interface: 2
number of zones: 102 (99 automatic)
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/900/1000
tcp clients: 0/150
TCP high-water: 0
server is up and running
No error this last try, looks like is working
inukaze
-
inukaze
- Black ninja
- Posts: 47
- Joined: 06 Jul 2023, 07:40
- Distribution: Slackware
Post#8
by inukaze » 15 Aug 2023, 22:23
beny wrote: ↑15 Aug 2023, 20:30
hi ,you are right, seem porteus do not start bind but slackware can do it
i think is because on Porteus does not exist default the group called "named" neither user called "named"
and becuase of that, is the question " Someone can tell me how i should create the user and group named default for Slackware64 15.0 ?" on the final on the first post on this thread.
inukaze
-
beny
- Full of knowledge
- Posts: 2098
- Joined: 02 Jan 2011, 11:33
- Location: italy
Post#9
by beny » 15 Aug 2023, 22:48
groupadd -g 20 named &&
useradd -c "BIND Owner" -g named -s /bin/false -u 20 named &&
install -d -m770 -o named -g named /srv/named
hi this is from linux from scratch take a look if work for you
https://www.linuxfromscratch.org/blfs/v ... /bind.html
root@porteus# groupadd named
root@porteus# useradd -c "BIND Owner" -g named -s /bin/false -u 20 named
root@porteus# install -d -m770 -o named -g named /srv/named
hi seem ok now..
beny
-
inukaze
- Black ninja
- Posts: 47
- Joined: 06 Jul 2023, 07:40
- Distribution: Slackware
Post#10
by inukaze » 16 Aug 2023, 13:16
Code: Select all
groupadd named
useradd -c "BIND Owner" -g named -s /bin/false -u 20 named
install -d -m770 -o named -g named /srv/named
Works fine
inukaze