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 and iscsi

Discussion in 'General Discussion' started by geddes2, Jul 26, 2006.

  1. geddes2

    geddes2 Member

    Joined:
    Jun 19, 2006
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    1
    Greetings hallowed and most honorable cpanelists,

    So, the latest stumbling block in my cpanel saga has had to do with dns resolution. Specifically, my named just doesn't work. It doesn't report any errors, it starts [ok] but it doesn't resolve any domain names. I noticed this because when wgeting and curling files, dns resolution took an abnormally long time. When I commented my server's own IP out of my resolv.conf, dns resolution was instantaneos. When my server's ip is the only line in resolv.conf, dns resolution fails completely.

    On my other cpanel box running the same setup (RHEL3) I did not experience this problem. The only difference between the two computers is that this one, with the problem, is attached to a SAN via iSCSI and has 3 network interfaces and 3 IP address, but 2 of those interfaces and IP addresses are useless and only connect to the SAN network. I am not sure and am not even sure where to begin - I can't even find a named.log file using the locate command. Any ideas about where I can start to solve this problem would be appreciated.

    Thank you in advance.
     
  2. geddes2

    geddes2 Member

    Joined:
    Jun 19, 2006
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    1
    I solved the problem by putting a forward directive in the named.conf - why is there no forward directive by default?
     
  3. jrehmer

    jrehmer Well-Known Member

    Joined:
    Apr 10, 2003
    Messages:
    287
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Denver, CO
    You should only need a forwarder if your named is not a caching name server, ie doesn't have the "." zone in the /etc/named.conf file.

    Is the DNS resolution working for the domains on your server? I'm assuming you are meaning that your DNS server is having trouble looking up other sites, and if so, look for a the root hint zone "." in your named.conf file, if it is not there that is why.
     
  4. claudio

    claudio Well-Known Member

    Joined:
    Jul 31, 2004
    Messages:
    201
    Likes Received:
    0
    Trophy Points:
    16
    for me named.conf was not loading or reloading customers dns zones

    they arent even declared there

    i run /scripts/fixndc

    i use centos3.4

    then i went into /etc and did a pico in named.conf

    there was no customer zone in there as i said

    i mv named.conf to named.conf.bak

    and edit named.conf.fixndc
    there was customers dns zones

    so i renamed cp named.con.fixndc named.conf

    and in the whm i restarted bind

    after this customers dns zones were loaded

    kind regards and good luck
     
Loading...

Share This Page