Sobald jedoch der resolved-service neugestartet wird oder der Server an sich neustartet, werden wieder die "alten" conf-Files hergestellt und die nicht funktionierenden IPs werden wieder eingetragen.
Wahrscheinlich ist dein /etc/resolv.conf ein symbolischer Link
Überprüfen:
ls -l /etc/resolv.confHello,
same problem with phishing of fake Netcup communications.
All messages are coming from different ip's, belonging to GHOSTNET GmbH:
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=89.144.5.240; helo=zapef.com; envelope-from=newsletter@zapef.com; receiver=<UNKNOWN>
Received: from zapef.com (unknown [89.144.5.240])
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=89.144.5.254; helo=zapef.com; envelope-from=newsletter@zapef.com; receiver=<UNKNOWN>
Received: from zapef.com (unknown [89.144.5.254])
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=89.144.5.240; helo=zapef.com; envelope-from=newsletter@zapef.com; receiver=<UNKNOWN>
Received: from zapef.com (unknown [89.144.5.240])
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=89.144.5.2; helo=zapef.com; envelope-from=newsletter@zapef.com; receiver=<UNKNOWN>
Received: from zapef.com (unknown [89.144.5.2])inetnum: 89.144.5.0 - 89.144.5.255
netname: GHOSTNET-FRA
descr: GHOSTNET GmbH
country: DE
blocking that CDIR segment is a good solution:
89.144.5.0/24
Geht weiter.
Nun von:
santeservicefondation.eu
65.21.141.111
same here just 30 minutes ago, from domain santeservicefondation.eu
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=65.21.141.111; helo=santeservicefondation.eu; envelope-from=contact-XXXXXXX@santeservicefondation.eu; receiver=<UNKNOWN>
Received: from santeservicefondation.eu (static.111.141.21.65.clients.your-server.de [65.21.141.111])
It seems they try to exploit one token session if we enter in:
https://www.customercontrolpanel-netcup.NOCLICK.....php?token=XX6d15d5-XXXX-XXXX-XXXXfc-XXX8b1b0e535
at least in my case the token is the same for different messages. Probably there is somebody keeping the property of that session, to stole information from a potential access using that token.
Maybe a typo? Make sure the IP and gateway are the same as in the SCP network tab. Otherwise they will not work.
you are right, the network tab information was different.
I have solved the issue.
Thanks so much!
Hello, gute Nacht,
I have a persistent failure in networking.service. Interface eth0 is working normally. I don't know the reason for this error and how to solve it:
# systemctl status networking.service
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-11-22 20:20:06 CET; 5s ago
Docs: man:interfaces(5)
Process: 31960 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Main PID: 31960 (code=exited, status=1/FAILURE)
nov 22 20:20:06 host.myhost.com systemd[1]: Starting Raise network interfaces...
nov 22 20:20:06 host.myhost.com ifup[31960]: RTNETLINK answers: File exists
nov 22 20:20:06 host.myhost.com ifup[31960]: ifup: failed to bring up eth0
nov 22 20:20:06 host.myhost.com systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
nov 22 20:20:06 host.myhost.com systemd[1]: networking.service: Failed with result 'exit-code'.
nov 22 20:20:06 host.myhost.com systemd[1]: Failed to start Raise network interfaces.final error says "Failed to start Raise network interfaces", although the interfaces are raised and working. I don't understand 
this is the interface configuration:
# cat /etc/etc/network/interfaces
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 89.58.57.125
netmask 255.255.255.0
gateway 89.58.57.1
dns-nameservers 1.1.1.1 1.0.0.1# cat /etc/network/interfaces.d/50-cloud-init.cfg
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 89.58.57.123/22
gateway 89.58.56.1When I comment all the lines inside file: 50-cloud-init.cfg, the server hangs and it doesn't work.
Should I keep file 50-cloud-init.cfg always active?
What is the right way to configure an static IP in Netcup and stop that error in networking.service?
thanks for any help!