The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

named issue - please help!

Discussion in 'General Discussion' started by luisp, Dec 12, 2006.

  1. luisp

    luisp Well-Known Member
    PartnerNOC

    Joined:
    Jan 17, 2003
    Messages:
    57
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Portugal
    cPanel Access Level:
    DataCenter Provider
    Hello,

    Every single day all the domains in my server stop resolving. Named is running but sites simple stop responding ( not even an nslookup in server via SSH works ).

    In logs i have :

    Dec 11 17:43:36 web14 named[30111]: client 128.243.44.10#32769: error sending response: host unreachable
    Dec 11 17:43:36 web14 named[30111]: client 212.27.54.205#18797: error sending response: host unreachable
    Dec 11 17:43:36 web14 named[30111]: client 212.27.53.204#18340: error sending response: host unreachable
    Dec 11 17:43:36 web14 named[30111]: client 207.126.144.115#40276: error sending response: host unreachable
    Dec 11 17:43:36 web14 named[30111]: client 211.91.216.129#1060: error sending response: host unreachable
    Dec 11 17:43:36 web14 named[30111]: client 203.144.207.14#32782: error sending response: host unreachable
    Dec 11 17:43:36 web14 named[30111]: client 61.90.153.250#5997: error sending response: host unreachable
    Dec 11 17:43:36 web14 named[30111]: client 143.90.130.183#39030: error sending response: host unreachable
    Dec 11 17:43:37 web14 named[30111]: client 143.90.129.55#35044: error sending response: host unreachable

    and more..

    Dec 12 13:39:01 web14 named[27439]: client 216.255.186.170#19824: error sending response: host unreachable
    Dec 12 13:39:01 web14 named[27439]: client 85.255.112.4#52590: error sending response: host unreachable

    Also, to stop / start named in ssh it take years. I dont know what else to do, and i have to restart named more then 10 times to have it working.

    Any suggestion?
     
  2. Spiral

    Spiral BANNED

    Joined:
    Jun 24, 2005
    Messages:
    2,023
    Likes Received:
    7
    Trophy Points:
    0
    Are any of the IPs shown above the IP addresses for your own server?

    (If not, those messages are not what you think and don't mean your DNS isn't working)

    Without more details from you though, just based on what I have seen above,
    I would be most inclined to think you have a firewall blocking port 53
     
    #2 Spiral, Dec 12, 2006
    Last edited: Dec 12, 2006
  3. luisp

    luisp Well-Known Member
    PartnerNOC

    Joined:
    Jan 17, 2003
    Messages:
    57
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Portugal
    cPanel Access Level:
    DataCenter Provider
    Hello,

    No that ips are not mine. Port 53 is opened.

    What do u suggest?
     
  4. luisp

    luisp Well-Known Member
    PartnerNOC

    Joined:
    Jan 17, 2003
    Messages:
    57
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Portugal
    cPanel Access Level:
    DataCenter Provider
    occurring again.

    any advice anyone?
     
  5. AndyReed

    AndyReed Well-Known Member
    PartnerNOC

    Joined:
    May 29, 2004
    Messages:
    2,222
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Minneapolis, MN
    As suggested earlier, make sure that Port 53 is open. Typically, a cPanel powered server (many other servers for that matter) have the following ports open:

    Code:
    PORT     STATE SERVICE
    1/tcp    open  tcpmux
    21/tcp   open  ftp
    25/tcp   open  smtp
    26/tcp   open  unknown
    53/tcp   open  domain
    80/tcp   open  http
    110/tcp  open  pop3
    111/tcp  open  rpcbind
    143/tcp  open  imap
    443/tcp  open  https
    465/tcp  open  smtps
    631/tcp  open  ipp
    783/tcp  open  hp-alarm-mgr
    953/tcp  open  rndc
    993/tcp  open  imaps
    995/tcp  open  pop3s
    3306/tcp open  mysql
    If you are using a firewall related application such as: APF, make sure Port 53 is inbound and outbound for both UDP and TCP connections. However, this may not be a firewall problem.

    Now, do you, by any chance, have any restrictions in /etc/named.conf file such as "allow-transfer" and/or "allow-recursion". If not, then the problem might be the /tmp partition (although not related but just in case). Are you mounting/umounting the /tmp partition? If yes, stop any services accessing /tmp including httpd and MySQL, umount /tmp and /var/tmp and then
    chmod 1777 /tmp
    Restart the services you stopped. Hope this helps!
     
    #5 AndyReed, Dec 13, 2006
    Last edited: Dec 13, 2006
Loading...

Share This Page