I am facing problems with the mydns with ispconfig3 in a remote server. The problem is my sites (eg http://www.thehumanape.org) are down on times although the server is up. Could not figure out any error message, too. Visitors report and I find sometimes that the site disappears even when I dig the site. When I ssh and check the servers all seem working fine, yet the site becomes unavailable. Any clue appreciated. Or do you suggest me to migrate to BIND9? Any hints to migrate to BIND9 from mydns with ISPConfig3 in Centos5? Thanks!
Are you sure it is a DNS issue? Did you check your logs, e.g. Apache's error log? Is this a physical server or a virtual machine?
Checked everything, not errors. But the mydns sometimes does not do what it needs to. It is a physical server.
This seems to be a problem with the syncing of the nameservers and not a problem of the master nameserver. the behaviour that you describe happens if the nameservers of a domain have different records so they delivere different IP addresses sometimes. Check all nameservers one by one if the deliver all the same IP address for a domain and all subdomains with dig. e.g. dig @ns1.yourdomain.tld yourdomain.tld dig @ns2.yourdomain.tld yourdomain.tld dig @ns3.yourdomain.tld yourdomain.tld
@Till: Thanks. As you suggested, I checked with the dig dig thehumanape.org dig www.thehumanape.org and they all give the same IP. But on times of days, dig does not work to my surprise. Just banging the head against the wall :-(
Code: mh1:~# dig ns1.thehumanape.org ; <<>> DiG 9.3.4 <<>> ns1.thehumanape.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38517 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;ns1.thehumanape.org. IN A ;; AUTHORITY SECTION: thehumanape.org. 86400 IN SOA ns1.thehumanape.org. mail.thehumanape.org. 2010091201 28800 7200 604800 86400 ;; Query time: 43 msec ;; SERVER: 213.133.99.99#53(213.133.99.99) ;; WHEN: Wed Oct 6 14:47:40 2010 ;; MSG SIZE rcvd: 78 mh1:~# dig ns2.thehumanape.org ; <<>> DiG 9.3.4 <<>> ns2.thehumanape.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49566 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;ns2.thehumanape.org. IN A ;; AUTHORITY SECTION: thehumanape.org. 86400 IN SOA ns1.thehumanape.org. mail.thehumanape.org. 2010091201 28800 7200 604800 86400 ;; Query time: 44 msec ;; SERVER: 213.133.99.99#53(213.133.99.99) ;; WHEN: Wed Oct 6 14:47:50 2010 ;; MSG SIZE rcvd: 82 mh1:~# It seems as if you didn't create A records for ns1.thehumanape.org and ns2.thehumanape.org.
Dear Falko: I have the following records created according to your suggestion: A mail 217.64.201.66 0 A ns1.thehumanape.org. 217.64.201.66 0 A ns2.thehumanape.org. 217.64.202.17 0 A thehumanape.org. 217.64.201.66 0 A www 217.64.201.66 0 MX thehumanape.org. mail.thehumanape.org. 10 NS thehumanape.org. ns1.thehumanape.org. 0 NS thehumanape.org. ns2.thehumanape.org. 0 Still the dig does not render the IP against the A records. zenny ***Support http://www.thehumanape.org ***
Did you change the nameservers? Code: mh1:~# dig ns thehumanape.org ; <<>> DiG 9.3.4 <<>> ns thehumanape.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37809 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;thehumanape.org. IN NS ;; ANSWER SECTION: thehumanape.org. 86400 IN NS [B][COLOR="Red"]ns1.freeregistrar.net[/COLOR][/B]. thehumanape.org. 86400 IN NS [B][COLOR="Red"]ns2.freeregistrar.net[/COLOR][/B]. ;; Query time: 31 msec ;; SERVER: 213.133.98.98#53(213.133.98.98) ;; WHEN: Thu Oct 7 15:04:15 2010 ;; MSG SIZE rcvd: 86 mh1:~# It's working now!
Falko: Yes I did change the nameservers. I removed two ns records for thehumanape.org. Thanks to Fabian of http://seeweb.it for guiding me. Thanks to you, too!!! zenny *** http://www.thehumanape.org ***
