Wolfgang Schweer:
[ Frank Weißer, 2022-01-26 ]
from tjener @school
root@tjener:~# service named status
● named.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor
preset: enabled)
Active: active (running) since Tue 2022-01-25 16:4
[ Frank Weißer, 2022-01-26 ]
> from tjener @school
>
> root@tjener:~# service named status
>
> ● named.service - BIND Domain Name Server
> Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor
> preset: enabled)
> Active: active (running) since Tue 2022-01-25 16:40:10 CET;
Hi Wolfgang,
now I face the same problem on two installations, the one @home and the
other @school.
Wolfgang Schweer:
(As of bullseye: 'service named status')
that's what I get:
from tjener @home
root@tjener:~# service named status
● named.service - BIND Domain Name Server
Loaded
[ Petter Reinholdtsen, 2022-01-10 ]
> Try 'ps -ef|grep bind' to see if the service is running, and 'service
> bind status' to see if the service reported something. Check
> /var/log/syslog for any errors.
(As of bullseye: 'service named status')
> No idea what is going on myself, I must admit.
[Frank Weißer]
> root@tjener:~# host vg.no 8.8.8.8
> Using domain server:
> Name: 8.8.8.8
> Address: 8.8.8.8#53
[...]
OK, so there is nothing blocking external DNS lookups.
Then I would guess the bind service is not working. No idea why, but do
'host localhost localhost' work, ie can the local D
Hi Petter,
with a unchanged etc/bind/named.conf.options:
root@tjener:~# host vg.no 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
vg.no has address 195.88.55.16
vg.no has address 195.88.54.16
vg.no has IPv6 address 2001:67c:21e0::16
vg.no mail is handled by 10 ALT4.ASPM
[Frank Weißer]
> I tried that with 10.0.0.1, 185.150.99.255 and, to go safe, 8.8.8.8
> No effect. My ISP (ewetel) doesn't tell anything about DNS's.
How did you test this? Did you remember to reload bind after each
change?
Is for example 'host vg.no 8.8.8.8' working on the main server?
> So m
Hi Petter,
I tried that with 10.0.0.1, 185.150.99.255 and, to go safe, 8.8.8.8
No effect. My ISP (ewetel) doesn't tell anything about DNS's.
And, with dhcp disabled on the router, WLAN- and LAN-clients as well as
DI of the network-installer work fine with 10.0.0.0/8 IP address,
default gateway
[Frank Weißer]
> the dhcp server on gateway (FRITZ!Box 7490) was definitely stopped
> before installation and stayed so. I installed from the netinstall image
> by entering network configuration manually when the automatic
> configuration failed due to missing dhcp server. That's the problem; wh
Hi Petter,
the dhcp server on gateway (FRITZ!Box 7490) was definitely stopped
before installation and stayed so. I installed from the netinstall image
by entering network configuration manually when the automatic
configuration failed due to missing dhcp server. That's the problem; why
are url
[Frank Weißer]
> What's going wrong?
Did you read the installation instructions in the manual on how to set
up the gateway?
It sound a bit like you have two competing DHCP servers, and neither is
giving you the setup you want.
--
Happy hacking
Petter Reinholdtsen
Hi,
looked nice,but maybe to nice :-(
after my 'solution' I was able to update tjener but couldn't login to
gosa anymore.
So my problem is still the same:
Tjener is installed and is able to reach addresses in the internet
after installation and BEFORE reboot.
After reboot gosa is availab
Hi again,
writing leads to thinking!
In my post I missed the entries of the lo device:
root@tjener:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
dns-search intern
dns-nameservers 127.0.0.1
and of
root@tjener:~# cat /etc/resolv.conf:
# Dynamic resolv.conf(5) file for gl
Hi Folks,
I've got a problem with a freshly installed tjener:
Fujitsu PRIMERGY TX100 S1, 8GB RAM
onboard Intel NIC (enp0s25 during installation)
PCIe Intel Fibre NIC (enp1s0)
The later should serve the 10.0.0.0/8 net, the copper one is in reserve.
Installation over fibre, getting 10.0.2.2 via d
14 matches
Mail list logo