Accéder au contenu principal

DNS cluster

 





Comment vérifeir le DNS ns1 vi putty

[20:23, 11/6/2024] Eyacine perso: systemctl status named

[20:23, 11/6/2024] E yacine perso: named.service - Berkeley Internet Name Domain (DNS)

   Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)

  Drop-In: /etc/systemd/system/named.service.d

           └─cpanel.conf

   Active: failed (Result: exit-code) since Wed 2024-11-06 19:30:07 CET; 41min ago

[20:24, 11/6/2024] Eyacine perso: journalctl -xe

[20:25, 11/6/2024] Ebyacine perso: /etc/named.conf:

[20:25, 11/6/2024] E yacine perso: nov. 06 20:15:26 ns1.e.dz systemd[1]: named.service: Control process exited, code=exited status=1

[20:26, 11/6/2024] Ebs yacine perso: nov. 06 20:15:26 ns1.s.dz bash[48307]: /etc/named.conf:1163: zone 'terrauboss.com': already exists previous definition: /etc/named.conf:1145

[20:26, 11/6/2024] E yacine perso: nov. 06 20:15:26 ns1.s.dz systemd[1]: named.service: Control process exited, code=exited status=1

[20:26, 11/6/2024] E yacine perso: nov. 06 20:15:26 ns1.s.dz systemd[1]: named.service: Failed with result 'exit-code'.

-- Subject: Unit failed



  •    54  2024-11-06 20:11:58 systemctl status bind
  •    55  2024-11-06 20:12:05 systemctl statusnamed
  •    56  2024-11-06 20:12:08 systemctl status named
  •    57  2024-11-06 20:12:23 systemctl restart  named
  •    58  2024-11-06 20:12:38 journalctl -xe
  •    59  2024-11-06 20:14:22 systemctl restart  named
  •    60  2024-11-06 20:14:29 systemctl stop   named
  •    61  2024-11-06 20:14:31 systemctl restart  named
  •    62  2024-11-06 20:14:41 vi /etc/named.conf
  •    63  2024-11-06 20:15:24 systemctl restart  named
  •    64  2024-11-06 20:15:39 journalctl -xe
  •    65  2024-11-06 20:16:49 vi /etc/named.conf
  •    66  2024-11-06 20:17:24 systemctl restart  named
  •    67  2024-11-06 20:17:35 systemctl status named
  •    68  2024-11-06 22:41:41 history






Commentaires

Enregistrer un commentaire

Posts les plus consultés de ce blog

Open Media Vault NAS change password

Known Root Password Login to the OMV using the root user and the current password via SSH or Console enter the following command passwd root The new password is now active. Unknown Root Password, but Admin Access to OMV GUI is Available In this scenario we still can help ourselves with the GUI. The method we use is, that we create a cron job for the root user which then resets the password. Navigate to System -> Cron Jobs Press the +Add button UN-tick the enabled box, so that the cronjob does not run automatically. put into the command field the following line, replace newpasswd with your password: echo "root:newpasswd" | chpasswd press okay select the newly created cron job Click the run button. in the opening window click the start button. It will shortly deactivate and activate again. open ssh or console and login as root with your new password. Root and Admin Password Unknown If you do not know the root password, you need to boot with a Li
Enregistrer un commentaire
Lire la suite

Zimbra install let's encrypt

 https://inguide.in/how-to-install-free-ssl-certificate-on-zimbra-mail-server/ Je change le domaine  ingu.pw In the article  Install Zimbra Mail Server o n CentOS 8, we learned to install Zimbra on CentOS. This article discusses the steps required to install the Let’s Encrypt free SSL certificate in Zimbra. Installing Free SSL Certificate on Zimbra: Method 1 This method is a proven one though you have to manually do all the steps. Another method discussed below is partially automatic, which might come in handy if you didn’t encounter any error during installation (working at the time of writing this article). So, let’s begin with method 1. First of all, add  epel repository  to the server 1 [root@mail ~]# yum -y install epel-release Install snapd Now, install  snapd  package with the following command 1 [root@mail ~]# sudo yum install snapd After the above step, you need to enable snapd. 1 [root@mail ~]# sudo systemctl enable --now snapd.socket Sometimes, the above command isn’t suffic
Enregistrer un commentaire
Lire la suite

cPanel DDOS attack - Mitigate Slowloris Attacks - mod_qos

Apache mod_evasive Mod_evasive is a module available for the Apache HTTP server that can automatically block attacks by rate-limiting any IP that sends too many requests in a short time. Start by installing the module from WHM’s  EasyApache 4  interface. Select the  Currently Installed Packages  profile, search for  mod_evasive  in the  Apache Modules  section, and then install it. The default settings are good for most servers, but you can tweak them further by editing the configuration file  /etc/apache2/conf.d/300-mod_evasive.conf . You can also whitelist specific IP addresses or classes, so legitimate requests are not blocked. Configure CSF to block attacks While  mod_evasive  works very well, it only protects the Apache webserver. In order to harden other services as well, you can install the free  ConfigServer Security & Firewall  (CSF), which also includes a WHM plugin. As the  root  user, install CSF with these terminal commands: cd /usr/src rm -fv csf.tgz wget https://down
Enregistrer un commentaire
Lire la suite