Hi all, Since about one week I met a serious problem with my dns server: no-one of the subdomain are accessible (sometimes it works, sometimes no). ns1.super-hebergement.fr is my ISPconfig host (dns host of this domain is not ISPconfig host itself but managed by OVH.net DNS) ns2.super-hebergement.fr point to the secondary dns service provide by Oneline.net, my dedicated server provider. Exemple with clips.super-h.fr: Not ambigous status: NXDOMAIN Another one: Better but doesn't explain the first result... My zone: My /etc/bind/pri.clips.super-h.fr: Nothing special so... In doubt: Sorry about my very poor english written, as you can see it, I'm a french guy
The problem appear with all my customers (about 60 subdomains), all others domains are ok. Example: Code: dig lescrapaudsdegigo.fr ; <<>> DiG 9.7.0-P1 <<>> lescrapaudsdegigo.fr ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57054 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;lescrapaudsdegigo.fr. IN A ;; ANSWER SECTION: lescrapaudsdegigo.fr. 86400 IN A 88.190.230.134 ;; AUTHORITY SECTION: lescrapaudsdegigo.fr. 86400 IN NS ns2.super-hebergement.fr. lescrapaudsdegigo.fr. 86400 IN NS ns1.super-hebergement.fr. ;; ADDITIONAL SECTION: ns1.super-hebergement.fr. 84302 IN A 88.190.230.134 ns2.super-hebergement.fr. 84302 IN A 88.191.254.71 ;; Query time: 12 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Mar 20 07:06:38 2012 ;; MSG SIZE rcvd: 140 Configuration of the parent zone: Code: zone "super-h.fr" { type master; allow-transfer {88.191.254.71;}; also-notify {88.191.254.71;}; file "/etc/bind/pri.super-h.fr"; }; /etc/bind/pri.super-h.fr: Code: $TTL 86400 @ IN SOA ns1.super-hebergement.fr. stephane.grillot.gmail.com. ( 2012031804 ; serial, todays date + todays serial # 28800 ; refresh, seconds 7200 ; retry, seconds 604800 ; expire, seconds 86400 ) ; minimum, seconds ; ftp.super-h.fr. 86400 A 88.190.230.134 mail 86400 A 88.190.230.134 ns1.super-h.fr. 86400 NS 88.190.230.134 super-h.fr. 86400 A 88.190.230.134 super-h.fr. 86400 MX 10 mail.super-h.fr. super-h.fr. 86400 NS ns1.super-hebergement.fr. super-h.fr. 86400 NS ns2.super-hebergement.fr. www 86400 A 88.190.230.134 dig super-h.fr: Code: dig super-h.fr ; <<>> DiG 9.7.0-P1 <<>> super-h.fr ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54033 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;super-h.fr. IN A ;; ANSWER SECTION: super-h.fr. 84138 IN A 88.190.230.134 ;; AUTHORITY SECTION: super-h.fr. 84138 IN NS ns2.super-hebergement.fr. super-h.fr. 84138 IN NS ns1.super-hebergement.fr. ;; ADDITIONAL SECTION: ns1.super-hebergement.fr. 84091 IN A 88.190.230.134 ns2.super-hebergement.fr. 84091 IN A 88.191.254.71 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Mar 20 07:10:09 2012 ;; MSG SIZE rcvd: 130 The only thing I plan to do is adding "IN A" entry in super-h.fr zone for all subdomains (one client = one subdomain) but until last week it works perfectly... Any idea?
Examples of sub-domains who didn't work: http://jdp2012.super-h.fr http://btslarochelle.super-h.fr http://websansfin.super-h.fr http://cercle-histoi...nies.super-h.fr http://aeevb.super-h.fr http://lessagittaires.super-h.fr http://sos-animaux.super-h.fr http://3bach-elec.super-h.fr http://ericf.super-h.fr http://tmm.super-h.fr http://cd31-tiralarc.super-h.fr http://redmine.super-h.fr http://cla.super-h.fr http://my-logo.super-h.fr http://e-a-j-d-burundi.super-h.fr http://fasolidaire.super-h.fr http://lecourrierdebovet.super-h.fr
Hello Falko, The problem is solved, my DNS provider was faulty, now I host my own two DNS servers but I have one more questions: I bought the ISPconfig guide to know more about mirror setup for DNS, I saw few things about it and it is not a slave/master cluster so, how does it work? Is it the good practice to configure a second dns server by this way (dns service with mirrir setrup of my first ISPconfig server?)? Regards,
Thats the recommended way when both servers run ispconfig. The dns records between the servers are synced internally by ispconfig, so this setup is asier then using the normal bind synchronisation.
