myDNS has stopped working

Discussion in 'Installation/Configuration' started by korbynn, Mar 9, 2010.

  1. korbynn

    korbynn Member

    I cannot access my websites or the control panel through domain names. Accessing the control panel through the IP works.

    I have rebooted the computer, restarted myDNS and apache but get the same results.

    It was working until 24 hours ago, but now I can not access the websites and others cannot access the websites.

    traceroute does not work from my computer because it cannot resolve the domain name but it resolves the ip directly.

    traceroute from other websites resolves the domain name and creates the report.

    I frustrated here. My clients are complaining that their sites are not accessable.

    Can anyone see jogarrard.com out there?

    What else can I look at to resolve this problem?
     
  2. korbynn

    korbynn Member

    I have also seen in /var/log/messages that myDNS has a high rejection rate of questions. Where does myDNS log this information? I know it is LOG_DAEMON but which file is this?

    CentOS 5.4.
    ISPConfig 3
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Mydns does not log by default. Please take a look in the mydns documentation for details on how to configure logging:

    http://mydns.bboy.net/doc/html/mydns_32.html#SEC32

    The log damon is the services that writes the syslog file on your server.
     
  4. korbynn

    korbynn Member

    To further this discussion, it looks like I need PTR records as part of the DNS records. I am not quite sure about the entries. Could someone show me what the proper values would look like for Name and Canonical Hostname.

    It appears that I need this values since myDNS seems to be rejecting requests since the PTR records are not found.
     
  5. korbynn

    korbynn Member

    myDNS is showing this type of stuff:

    mydns: 09-Mar-2010 19:11:00+983651 #592 54190 UDP 80.249.96.10 IN PTR 49.39.46.64.in-addr.arpa. REFUSED Zone_not_found 1 0 0 0 LOG Y QUERY ""
    mydns: 09-Mar-2010 19:11:01+157787 #593 43795 UDP 80.249.96.10 IN PTR 49.39.46.64.in-addr.arpa. REFUSED Zone_not_found 1 0 0 0 LOG Y QUERY ""
    mydns: 09-Mar-2010 19:11:01+335192 #594 32758 UDP 80.249.111.5 IN PTR 49.39.46.64.in-addr.arpa. REFUSED Zone_not_found 1 0 0 0 LOG Y QUERY ""
    mydns: 09-Mar-2010 19:11:06+093321 #595 30429 UDP 67.69.184.15 IN A www.fredandsharonsmovies.com. NOERROR - 1 1 0 0 LOG N QUERY ""
    mydns: 09-Mar-2010 19:11:22+560697 #596 19056 UDP 213.235.193.66 IN A ns0.korbynn.net. NXDOMAIN No_matching_resource_records 1 0 1 0 LOG N QUERY ""
    mydns: 09-Mar-2010 19:11:22+750336 #597 59783 UDP 213.235.193.66 IN A ns0.korbynn.net. NXDOMAIN No_matching_resource_records 1 0 1 0 LOG Y QUERY ""
    mydns: 09-Mar-2010 19:11:24+955711 #598 17307 UDP 65.55.5.136 IN A ns0.korbynn.com. NXDOMAIN No_matching_resource_records 1 0 1 0 LOG N QUERY ""
    mydns: 09-Mar-2010 19:11:24+997157 #599 64397 UDP 65.55.5.136 IN A ns1.korbynn.com. NXDOMAIN No_matching_resource_records 1 0 1 0 LOG N QUERY ""


    Does anyone know what is going on here?

    Any help is appeciated.:confused:
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Have you created a DNS A-Record for ns0.korbynn.net. (incl. the dot at the end!) in ispconfig?
     
  7. korbynn

    korbynn Member

    Thanks, I will add the period on the end of the domain name.

    The solution that seemed to work was that I did a 'php update.php' from the ispconfig download. The sites suddenly came alive after that, maybe some files got corrupted/modified that should not have.

    Is there a command sequence that would compare differences in the downloaded with the installed? Like a consistency check.
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    No, we dont have a script for a consistency check. The update.php script replaces all files, so you should have correct files now.
     
  9. korbynn

    korbynn Member

    It appears that ISPConfig already places a period at the end of the domain name.
     

Share This Page