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.

Server issues...

Discussion in 'General Discussion' started by c3uc3, Jun 6, 2005.

  1. c3uc3

    c3uc3 Member

    Joined:
    Aug 15, 2004
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    Did a lookup at DNSreport.com on my server and domain name.

    Been having quite a bit of problem with my server since shifting my IPS.
    Mails have been moving slowly.

    Found one of the few issues listed on the report:

    Could this be causing my mail to be slow?
    --------------------------------
    WARN No NS A records at nameservers WARNING: Your nameservers do not include any corresponding A records when asked for your NS records. They probably are not returning the A records when asked, which can prevent some other DNS servers from contacting your DNS servers. The problem record(s) are:
    Nameserver 203.124.116.72 did not provide any IPs
    Nameserver 203.124.116.73 did not provide any IPs
    --------------------------------
    WARN Nameservers on separate class C's WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C (technically, /24) address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
    --------------------------
    FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:
    73.116.124.203.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]
    ------------------------------

    Can anyone advise on this?
     
  2. dalem

    dalem Well-Known Member
    PartnerNOC

    Joined:
    Oct 24, 2003
    Messages:
    2,577
    Likes Received:
    40
    Trophy Points:
    48
    Location:
    SLC
    cPanel Access Level:
    DataCenter Provider
    yes

    add a records for both your nameservers

    Have your data center set up reverse ptr for your servers IP with your hostname
     
  3. c3uc3

    c3uc3 Member

    Joined:
    Aug 15, 2004
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    Can anyone guide to "add a records for both your nameservers ".
     
  4. dalem

    dalem Well-Known Member
    PartnerNOC

    Joined:
    Oct 24, 2003
    Messages:
    2,577
    Likes Received:
    40
    Trophy Points:
    48
    Location:
    SLC
    cPanel Access Level:
    DataCenter Provider
    WHM
    edit set up

    scroll down to where your name servers are listed

    click button add A record for your nameservers

    done
     
  5. c3uc3

    c3uc3 Member

    Joined:
    Aug 15, 2004
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    Tried however the following shows up....

    Zone com.sg does not exist, a new zone for ns2.fusevision.com.sg will be created.
    Sorry, a DNS entry for ns2.fusevision.com.sg already exists, please delete it first Add Complete
     
  6. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    You should, in WHM:

    1. Delete the zone for ns2.fusevision.com.sg (and any other ns*.fusevision.com.sg zones)

    2. Then edit the zone for fusevision.com.sg and simple ad A records for ns2 and any other ns* domains that you use and point them to the appropriate IP address(es).
     
  7. c3uc3

    c3uc3 Member

    Joined:
    Aug 15, 2004
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    I have this inside my zone dns for fusevision.com.sg

    ns1 203.124.116.72
    ns2 203.124.116.73

    Should it instead actually be

    ns1.fusevision.com.sg 203.124.116.72
    ns2.fusevision.com.sg 203.124.116.73

    I added in the above however I also retained ns1 203.124.116.72 ns2 203.124.116.73

    Which do I actually keep? Thanks!
     
  8. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    Keep the first ones. The second ones are actually incorrect as you have them and will be causing problems (the FQDN must end in a dot), i.e.:

    ns1.fusevision.com.sg. 203.124.116.72
    ns2.fusevision.com.sg. 203.124.116.73
     
Loading...

Share This Page