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.

Nameserver Issue(s)

Discussion in 'Bind / DNS / Nameserver Issues' started by ChiefGoFor, Apr 24, 2008.

  1. ChiefGoFor

    ChiefGoFor Registered

    Joined:
    May 8, 2007
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Well, I have spent most of the day reading threads without any luck. Hopefully, someone will be able to look at this information and say, "Duh, this needs to be changed to that".

    -----

    WHM 11.15.0
    FEDORA 8 i686 on vmware

    -----

    I have a domain set up to be used for a Nameserver at Godaddy. We will call it: chiefgofordns.com (this is not the actual domain name)

    I only have one domain installed on the server. We will call it: myfirstdomain.com this is not the actual domain name)

    -----

    ns1.chiefgofordns.com points to a PLESK server ip and works (not the one having issues)
    ns2.chiefgofordns.com points to a PLESK server ip and works (not the one having issues)
    ns3.chiefgofordns.com points to the WHM server main ip (139.xxx.xxx.34)
    ns4.chiefgofordns.com points to the WHM server ip (139.xxx.xxx.35)

    When I "ping" ns3.chiefgofordns.com using a windows command prompt, I get a reply (most of the time).
    When I "ping" ns4.chiefgofordns.com using a windows command prompt, I do NOT get a reply. (that's odd)
    * More info on these settings using a DNS lookup tool at the very bottom.

    -----

    Primary Nameserver: ns3.chiefgofordns.com
    Secondary Nameserver: ns4.chiefgofordns.com

    -----

    Under "Network Setup"->"Nameserver IPs", I see the following information:

    Ip Nameserver
    139.xxx.xxx.34 ns3.chiefgofordns.com
    139.xxx.xxx.35 ns4.chiefgofordns.com

    -----

    I have three DNS Zones:
    myfirstdomain.com
    ns3.chiefgofordns.com
    ns4.chiefgofordns.com

    <<myfirstdomain.com>>
    myfirstdomain.com. 86400 NS ns3.chiefgofordns.com.
    myfirstdomain.com. 86400 NS ns4.chiefgofordns.com.
    myfirstdomain.com. 14400 A 139.xxx.xxx.34
    localhost.myfirstdomain.com. 14400 A 127.0.0.1
    www 14400 CNAME myfirstdomain.com.
    Other CNAME and MX records omited since I do not think they apply.

    <<ns3.chiefgofordns.com>>
    ns3.chiefgofordns.com. 86400 NS ns3.chiefgofordns.com.
    ns3.chiefgofordns.com. 86400 NS ns4.chiefgofordns.com.
    ns3.chiefgofordns.com. 14400 A 139.xxx.xxx.34
    localhost.ns3.chiefgofordns.com. 14400 A 127.0.0.1

    <<ns4.chiefgofordns.com>>
    ns4.chiefgofordns.com. 86400 NS ns3.chiefgofordns.com.
    ns4.chiefgofordns.com. 86400 NS ns4.chiefgofordns.com.
    ns4.chiefgofordns.com. 14400 A 139.xxx.xxx.35
    localhost.ns3.chiefgofordns.com. 14400 A 127.0.0.1

    -----

    Using DIG online, I can up with the following (http://www.menandmice.com/knowledgehub/tools/dig):

    ; <<>> DiG 9.2.3 <<>> @dns1.menandmice.com myfirstdomain.com ANY
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9243
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
    ;; QUESTION SECTION:
    ;myfirstdomain.com. IN ANY
    ;; ANSWER SECTION:
    myfirstdomain.com. 155232 IN NS ns3.chiefgofordns.com.
    myfirstdomain.com. 155232 IN NS ns4.chiefgofordns.com.
    ;; AUTHORITY SECTION:
    myfirstdomain.com. 155232 IN NS ns4.chiefgofordns.com.
    myfirstdomain.com. 155232 IN NS ns3.chiefgofordns.com.
    ;; ADDITIONAL SECTION:
    ns3.chiefgofordns.com. 155232 IN A 139.xxx.xxx.34
    ns4.chiefgofordns.com. 155232 IN A 139.xxx.xxx.35
    ;; Query time: 145 msec
    ;; SERVER: 217.151.171.7#53(dns1.menandmice.com)
    ;; WHEN: Thu Apr 24 18:38:19 2008
    ;; MSG SIZE rcvd: 146


    -----

    Any advise is GREATLY appreciated. Thank you!
     
  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
  3. ChiefGoFor

    ChiefGoFor Registered

    Joined:
    May 8, 2007
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
  4. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    I'm not a technical analyst, but I have seen all kinds of issues crop up when people attempt to install cPanel/WHM on unsupported distributions or even simply unsupported versions of distributions we support.
     
  5. ChiefGoFor

    ChiefGoFor Registered

    Joined:
    May 8, 2007
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Anyone else have any thoughts on something I should check?
     
Loading...

Share This Page