Nameservers, DynDNS, Local DNS

[BorderAmigos]

My ISP has taken to changing my address, which is their right. I was set up with zones for all my domains on my registrars DNS. And would have to change them all every time the IP changes which is a pain. My registrar does not support dynamic DNS so I opened an account with DynDNS.com.

I changed the name server with my registrar for my main domain to the DynDNS nameservers. I set up A records there for the domain, www, ftp, ns1 and ns2. This is all working fine for the main domain.

Also I changed my other domain names with my registrar to point to the ns1 and ns2 of my main domain. These are resolving now to my internal IP address, 10.0.0.100. I am guessing that I needed to change the DNS in ISPConfig to the external address now instead of the internal one. I did this and don't see an immediate fix but may need wait for net propagation.

Is the above correct? If so, since I am running a local client via cron to update the DynDNS service, is there a way I can update the local DNS automatically at the same time? For example, modifying their client to rewrite the dns conf file(s).

(DynDNS charges for each custom domain name so obviously I only want one there and the other thirty four locally).

[BorderAmigos]

After a little propagation time what I did above seems to be working. So my main question is how to update the local DNS when my external IP changes. There is an nsupdate utility with BIND 8 and 9 which I may try but not sure if it will conflict with ISPConfig.

I need to add an 'allow update...' in the zone files. Will ISPConfig overwrite this in the pri.www.example.com files? If so, in what part of the script is that in, make_vhosts() or similar?

Maybe this should be in developer thread if not relevant here.

[falko]

Will ISPConfig overwrite this in the pri.www.example.com files?
Yes, but you can modify the templates in /root/ispconfig/isp/conf - please save the modified templates in /root/ispconfig/isp/conf/customized_templates.

[BorderAmigos]

I assume named.conf.master and pri.domain.master are the templates of interest in this case. So putting copies into customized_templates will read the custom ones instead of the defaults? Cool.

Another question, if I uncheck 'create dns' on a site and co-domain after it is up and running will that prevent ISPConfig from rewriting pri.domain.conf for that domain?

PS - I like your photos of Antigua, brings back some memories of visiting there.

[falko]

Another question, if I uncheck 'create dns' on a site and co-domain after it is up and running will that prevent ISPConfig from rewriting pri.domain.conf for that domain?Yes, but it will still rewrite the files if you change the data on the DNS Manager.

PS - I like your photos of Antigua, brings back some memories of visiting there.I would have made more photos, but unfortunately my camera didn't like the wet and hot climate...:rolleyes: