Thank you. Actually, I haven't touched anything and it worked all by itself. Now xyz.com shows standard ISPconfig's index.html start page. Guess DNS had to propagate. Could it be due to DNS propagation? But this happened to me on other domains as well and now I know what to look for. All my domains are set to an IP, not * and I use nginx, not Apache. Regarding your guidance that all domain names should end with the dot: even if I don't add the dot at the end, ISPconfig adds it automatically. Follow up: Should I put IP of ISPconfig #2 in "Allow zone transfers to these IPs" on ISPconfig #1? I did but mxtoolbox.com reports "Serial numbers do not match". Is it because of that?
One more thing, please: I can set my NS's to ns1.mydomain.com and ns2.mydomain.com to any domain EXCEPT for mydomain.com? Because I just did that and mydomain.com and all of its subdomains (including ns1 and ns2) became unavailable. I could access ISPconfig #1 and #2 only via IP address.
Yes. That basically the hen <> egg problem. to resolve the subdomain ns1.mydomain.com, you must know the dns server of the zone mydomain.com. But you cant do that as the the nameserver is a subdomain of the same zone. http://en.wikipedia.org/wiki/Domain_Name_System#Circular_dependencies_and_glue_records There is a solution for that, it is named a glue record. This means that you have to add an a-record for ns1 and ns2 at the domain regitsry of the domain, so this a-record gets stored in the root nameservers.
Thank you. I was thinking exactly that: hen <> egg But I am pretty sure I entered the glue records. Maybe just needs more time to propagate. On a side note: shouldn't the text when adding secondary DNS zone be "Allow zone transfers FROM these IPs (comma separated list)" since you should add the IP address of the first/primary NS? How long does it take for the secondary zone server to pick up what the primary is sending? Because it has been a little under 12 hours since I configured both primary and secondary DNS zone and mxtools.com is reporting: "At least one name server failed to respond in a timely manner; Failure detail: IP of secondary zone server"
It has been almost 48 hours since I configured primary and secondary DNS zone and mxtools.com still reports the same: Code: At least one name server failed to respond in a timely manner Failure detail: IP address of the ISPconfig server with secondary DNS zone configured Please help
Is this it: Code: Feb 18 11:20:45 vps named[512]: zone [I]mydomain.com[/I]/IN: refresh: unexpected rcode (SERVFAIL) from master [I]secondary dns server IP[/I]#53 (source 0.0.0.0#0) Im not sure where to look for syslog.
Bind logs all ist errors into the syslog file of the server. Check the syslog of the master and the slave server.
I have finally managed to work this out. Bellow is the screenshot of my configuration on both servers for future reference for anyone struggling like me.
A while ago I made a guide in my personal KB on how to do that with VestaCP. I think it's really straight forward and easy to follow. It's more or less the same you have to do for ISPConfig. Might also be of help to anyone confused: https://kb.ympker.net/knowledgebase/vestacp-setup-nameserversdns-properly/
