1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

name server setup

Discussion in 'Plesk for Linux - 8.x and Older' started by jpwdesigns, Feb 11, 2007.

  1. jpwdesigns

    jpwdesigns Guest

    Hi im having a bad time trying to set up name servers on my box. Plesk 8.1.0

    firewall is not an issue and ive set up a ns3.jpwns.com and ns4.jpwns.com with godaddy pointing to 2 ip addresses on this box. then in the server > DNS panel i created the a records for ns3.jpwns.com and ns4.jpwns.com

    I can ping ns3. and ns4. and it resolves to the right ip address but if i try to query the dns server it times out. Named is started, and firewall not blocking 53. why would it time out? testing on a domain i set up phuketforsale.info on this box.

    Thanks for any help. im new at setting up name servers obviously.

  2. phoenixisp

    phoenixisp Silver Pleskian

    Feb 2, 2002
    Likes Received:
    Can you post all of your DNS settings for that domain?
  3. jpwdesigns

    jpwdesigns Guest

    DNS settings

    Yeah, here's everything

    Server > DNS:

    <domain>. NS ns3.jpwns.com.
    <domain>. NS ns4.jpwns.com.
    <domain>. A <ip>
    <domain>. MX (10) mail.<domain>.
    <ip> / 24 PTR <domain>.
    ftp.<domain>. CNAME <domain>.
    mail.<domain>. A <ip>
    webmail.<domain>. A <ip>
    www.<domain>. CNAME <domain>.

    Domains > Phuketforsale.info > DNS / 24 PTR phuketforsale.info.
    ftp.phuketforsale.info. CNAME phuketforsale.info.
    mail.phuketforsale.info. A
    phuketforsale.info. NS ns3.jpwns.com.
    phuketforsale.info. NS ns4.jpwns.com.
    phuketforsale.info. A
    phuketforsale.info. MX (10) mail.phuketforsale.info.
    webmail.phuketforsale.info. A
    www.phuketforsale.info. CNAME phuketforsale.info.

    (dont know if it matters but...) Domains > jpwns.com > DNS: / 24 PTR jpwns.com.
    ftp.jpwns.com. CNAME jpwns.com.
    jpwns.com. NS ns3.jpwns.com.
    jpwns.com. NS ns4.jpwns.com.
    jpwns.com. A
    jpwns.com. MX (10) mail.jpwns.com.
    mail.jpwns.com. A
    ns1.jpwns.com. A
    ns2.jpwns.com. A
    ns3.jpwns.com. A
    ns4.jpwns.com. A
    webmail.jpwns.com. A
    www.jpwns.com. CNAME jpwns.com.

    Thanks in advance
  4. phoenixisp

    phoenixisp Silver Pleskian

    Feb 2, 2002
    Likes Received:
    You have some serious issues. I would suggest using dnsstuff.com to get started. I ran a DNS check for you and found these problems:

    WARN All nameservers report identical NS records WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed). returns 0 answers (may be a referral) returns 0 answers (may be a referral)

    FAIL All nameservers respond ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:

    Note: If you are running a Watchguard Firebox with DNS Proxy enabled, there may be a bug causing port numbers get mixed up -- if this is the case, you can contact Watchguard to see if they have a fix.

    FAIL Lame nameservers ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:

    FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:

    FAIL No NSs with CNAMEs ERROR: I checked to see if there were any CNAMEs for your NS records (there shouldn't be), but they all timed out. Note: This test checks with our local DNS server (since the NS record hostnames may not be handled by your DNS server), and therefore may be cached.

    WARN TCP Allowed WARNING: One or more of your DNS servers does not accept TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. The problem servers are: Error [No response to TCP packets]. Error [No response to TCP packets].

    SOA FAIL SOA Record No valid SOA record came back:
    is not jpwns.com.
    It is not related, but you should not have more than one PTR record per IP address.

    I hope this gets you started. If not I would contact your ISP.
  5. jpwdesigns

    jpwdesigns Guest


    Thanks Phoenix.