Hi, I migrated an ISPC2 to a new server this week-end (posted a few threads about this) and everything went fine until this morning. The DNS info was propagating fine until yesterday night (which was the 72 hours limit for propagation). This morning, all the domains point to the old server again, meaning nowhere. My setup is as follow : - The ISPC3 server numerizen.com (machine hostname) is the primary DNS server. - ns6.gandi.net is the secondary server. - My hosting provider has an interface to set up a glue record, which is now the IP of new the server. - The domain name of the DNS server is dns.numerizen.com. Here is the zone file for numerizen.com : $TTL 86400 @ IN SOA dns.numerizen.com. vb.numerizen.com. ( 2014091371 ; serial, todays date + todays serial # 28800 ; refresh, seconds 7200 ; retry, seconds 604800 ; expire, seconds 86400 ) ; minimum, seconds ; aaesff 86400 A 92.243.19.62 adonis 86400 A 92.243.19.62 aedilis 86400 A 92.243.19.62 ajax 86400 A 92.243.19.62 alabm 86400 A 92.243.19.62 almede 86400 A 92.243.19.62 archipels 86400 A 92.243.19.62 averell.da 86400 A 92.243.19.62 avispneumo 86400 A 92.243.19.62 azonic 86400 A 92.243.19.62 bioberbere 86400 A 92.243.19.62 bugs 86400 A 92.243.19.62 cartaro 86400 A 92.243.19.62 catbook 86400 A 92.243.19.62 cc 86400 A 92.243.19.62 chattermark 86400 A 92.243.19.62 couture 86400 A 92.243.19.62 css.test.recma 86400 A 95.142.171.122 ctmk 86400 A 92.243.19.62 d6 86400 A 92.243.19.62 d8 86400 A 92.243.19.62 da 86400 A 92.243.19.62 dc 86400 A 92.243.19.62 demo 86400 A 92.243.19.62 dev 86400 A 92.243.19.62 devec 86400 A 92.243.19.62 devrecma 86400 A 92.243.8.236 dns 86400 A 92.243.19.62 drupal 86400 A 92.243.19.62 ec 86400 A 92.243.19.62 elsevier 86400 A 92.243.8.236 esperluete 86400 A 92.243.19.62 etude 86400 A 92.243.19.62 fild7 86400 A 92.243.19.62 filoeuvre 86400 A 92.243.19.62 fk 86400 A 92.243.19.62 gd7 86400 A 92.243.19.62 glossaire 86400 A 92.243.19.62 grafbook 86400 A 92.243.19.62 hv 86400 A 92.243.19.62 ilm 86400 A 92.243.19.62 img.test.recma 86400 A 95.142.171.122 irht 86400 A 92.243.19.62 jack.da 86400 A 92.243.19.62 joe.da 86400 A 92.243.19.62 js.test.recma 86400 A 95.142.171.122 leitax 86400 A 92.243.19.62 libraria 86400 A 92.243.19.62 magpatients 86400 A 92.243.19.62 marc 86400 A 92.243.19.62 meeting 86400 A 92.243.19.62 notaires 86400 A 92.243.19.62 numerizen.com. 86400 A 92.243.19.62 old 86400 A 92.243.19.62 oldrecma 86400 A 92.243.8.236 pepart 86400 A 92.243.19.62 prestashop 86400 A 92.243.19.62 projet 86400 A 92.243.19.62 projets 86400 A 92.243.19.62 recma 86400 A 92.243.8.236 rudy 86400 A 92.243.19.62 sandbox 86400 A 92.243.19.62 skr 86400 A 92.243.19.62 solairegie 86400 A 92.243.19.62 symfony 86400 A 92.243.19.62 td 86400 A 92.243.19.62 test.recma 86400 A 95.142.171.122 tilly 86400 A 92.243.19.62 urmk 86400 A 92.243.19.62 uro 86400 A 92.243.19.62 vertika 86400 A 92.243.19.62 video-els 86400 A 92.243.19.62 vs 86400 A 92.243.19.62 web 86400 A 92.243.19.62 wiking 86400 A 92.243.19.62 william.da 86400 A 92.243.19.62 www 86400 A 92.243.19.62 *.migrate 86400 CNAME 92.243.19.62. numerizen.com. 86400 MX 10 web.numerizen.com. numerizen.com. 86400 NS dns.numerizen.com. numerizen.com. 86400 NS ns6.gandi.net. numerizen.com. 86400 TXT "v=spf1 a mx ptr ~all" Here are the dig results : dig numerizen.com ; <<>> DiG 9.8.3-P1 <<>> numerizen.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62556 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;numerizen.com. IN A ;; ANSWER SECTION: numerizen.com. 73453 IN A 92.243.19.62 ;; Query time: 28 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Sep 16 07:35:50 2014 ;; MSG SIZE rcvd: 47 dig dns.numerizen.com ; <<>> DiG 9.8.3-P1 <<>> dns.numerizen.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28445 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;dns.numerizen.com. IN A ;; ANSWER SECTION: dns.numerizen.com. 84802 IN A 92.243.14.107 ;; Query time: 29 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Sep 16 07:36:39 2014 ;; MSG SIZE rcvd: 5 ... which is insane : it was OK since the new server went live. Besides : dig @numerizen.com dns.numerizen.com ; <<>> DiG 9.8.3-P1 <<>> @numerizen.com dns.numerizen.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46300 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;dns.numerizen.com. IN A ;; ANSWER SECTION: dns.numerizen.com. 86400 IN A 92.243.19.62 ;; AUTHORITY SECTION: numerizen.com. 86400 IN NS ns6.gandi.net. numerizen.com. 86400 IN NS dns.numerizen.com. ;; Query time: 26 msec ;; SERVER: 92.243.19.62#53(92.243.19.62) ;; WHEN: Tue Sep 16 07:40:51 2014 ;; MSG SIZE rcvd: 92 A random domain hosted on the new server : dig filoeuvre.com ; <<>> DiG 9.8.3-P1 <<>> filoeuvre.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5264 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;filoeuvre.com. IN A ;; ANSWER SECTION: filoeuvre.com. 86400 IN A 92.243.14.107 ;; Query time: 29 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Sep 16 07:27:59 2014 ;; MSG SIZE rcvd: 47 I shut up bind, postfix and ispconfig on the old server two days ago, to make sure it can't interfere. All my websites are down, so it's very important for me ...
Maybe your secondray dns server did not pick up the changes. is the IP 92.243.19.62 the old or new one? check your dns e.g. at intodns.com, the site will show you if records differ between primary and secondary dns and it will show you which dns servers are delivering the records.
Sorry for the ambiguïty : 92.243.19.62 is the IP of the new one. The service you indicated (which I would have enjoyed knowing before) staes there is a discrepancy on the serials between primary and secondary. Should I update the primary ? But with what value ? For the record : http://www.intodns.com/numerizen.com
Ok, so the secondary dns did not pick up the updates. Try to add the ip address of the secondary dns server in the "allow zone transfer to" field of the dns zone and save. then wait a few minutes and test again with intodns.
Check with intodns after you give it a few minutes time, this info is not stored in the zone file, it is saved in named.conf.local, so it is not listed in your post above.
intodns seems happy now. Side question : will it take the normal time to propagate, or will it be a tad faster as only the secondary DNS was wrong ?
The time depends on the ttl of the dns zone. Also some client will already get the correct zone, it depends on which dns server is queried by the client.
Sorry, just a doubt : I don't need to do this for each and every domain right ? Only for the 'main' domain, where the DNS subdomain sits ?
You have to do this for all domains. You can do this also with sql, change the xfer field of all domains in the dns_soa table and then use the resync tool to apply the changes.
