Hostname Not Resolving. No Searched For Solution Working.

kray

• August 24, 2015 09:27

My main hostname is not resolving. The following pastes show everything I've done to research the problem which I've done in great detail. I don't understand why it's not resolving: hastebin.com/nutefebavu.dos

• 

  kernow

  • August 24, 2015 15:54

  Try :
  service named restart
  

  0
• 

  kray

  • August 24, 2015 16:00

  Try :
  service named restart
  

  
  I'm using a cluster of 2 dedicated dnsonly servers. named was not running on my main webserver. After running that command now it is. I don't think it's supposed to is it? Please examine my hastebin post. Here's what just happened: root@starfrost [~]# pgrep named root@starfrost [~]# root@starfrost [~]# service named restart Redirecting to /bin/systemctl restart named.service root@starfrost [~]# pgrep named 399360 root@starfrost [~]# reboot ----------------- root@starfrost [~]# pgrep named root@starfrost [~]#

  0
• 

  kray

  • August 24, 2015 16:09

  To understand what's going on you really have to see my post: hastebin.com/nutefebavu.dos I've also created a complimentary ticket #7052385 (Awaiting response).

  0
• 

  kernow

  • August 24, 2015 16:17

  Ah, OK. You can run
  service named stop
  Is the hostname listed in /etc/sysconfig/network ?

  0
• 

  kray

  • August 24, 2015 16:19

  Ah, OK. You can run
  service named stop
  Is the hostname listed in /etc/sysconfig/network ?

  
  Nothing is in there really:
  root@starfrost [~]# cat /etc/sysconfig/network # Created by anaconda root@starfrost [~]#
  This is the latest Centos 7.1 upgraded to the latest CloudLinux. Also, I don't think NetworkManager uses that file anymore.

  0
• 

  cPanelMichael

  • September 01, 2015 15:04

  Hello :) Per the support ticket, the issue was addressed by enabling clustering for the cPanel server in question, and by syncing the zones to the cluster. Feel free to let us know if you encounter any additional issues. Thank you.

  0

Please sign in to leave a comment.