Having trouble with updating settings in ISPC3

[todx]

I tried to change my dns setting by changing the ip of a domain i'm using. As far as I know it should take 1 minutes for changes to take effect, but nothing happened even after 5 minutes. So I ran a debug and it outputs the following:

15.11.2012-11:55 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
15.11.2012-11:55 - DEBUG - Found 2 changes, starting update process.
15.11.2012-11:55 - DEBUG - Calling function 'update' from plugin 'apps_vhost_plugin' raised by event 'server_update'.
15.11.2012-11:55 - DEBUG - Calling function 'update' from plugin 'network_settings_plugin' raised by event 'server_update'.
15.11.2012-11:55 - DEBUG - Network configuration disabled in server settings.
15.11.2012-11:55 - DEBUG - Calling function 'update' from plugin 'postfix_server_plugin' raised by event 'server_update'.
15.11.2012-11:55 - DEBUG - Processed datalog_id 2240
15.11.2012-11:55 - DEBUG - Calling function 'update' from plugin 'apps_vhost_plugin' raised by event 'server_update'.
15.11.2012-11:55 - DEBUG - Calling function 'update' from plugin 'network_settings_plugin' raised by event 'server_update'.
15.11.2012-11:55 - DEBUG - Network configuration disabled in server settings.
15.11.2012-11:55 - DEBUG - Calling function 'update' from plugin 'postfix_server_plugin' raised by event 'server_update'.
15.11.2012-11:55 - DEBUG - Processed datalog_id 2241
15.11.2012-11:55 - DEBUG - Calling function 'restartHttpd' from module 'web_module'.
15.11.2012-11:55 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock

The output of debug seems fine to me at least. Any ideas?

[till]

The debug output does not contain any dns related lines so it must have ben executed after the dns changes were written to disk. Please follow the instructions from this post http://www.howtoforge.com/forums/showthread.php?t=58408 and disable the cronjob before you change the dns record and the run the server.sh script and post the output.

[todx]

Alright, I disabled cronjob, under server config I set the loglevel to "debug" and made the necessary adjustments in ISPC3 and ran the "/usr/local/ispconfig/server/server.sh" and got this output:

15.11.2012-12:07 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
15.11.2012-12:07 - DEBUG - Found 2 changes, starting update process.
15.11.2012-12:07 - DEBUG - Calling function 'soa_update' from plugin 'bind_plugin' raised by event 'dns_soa_update'.
15.11.2012-12:07 - DEBUG - Writing BIND domain file: /etc/bind/pri.filerift.com
15.11.2012-12:07 - DEBUG - Writing BIND named.conf.local file: /etc/bind/named.conf.local
15.11.2012-12:07 - DEBUG - Processed datalog_id 2243
15.11.2012-12:07 - DEBUG - Calling function 'rr_update' from plugin 'bind_plugin' raised by event 'dns_rr_update'.
15.11.2012-12:07 - DEBUG - Writing BIND domain file: /etc/bind/pri.filerift.com
15.11.2012-12:07 - DEBUG - Writing BIND named.conf.local file: /etc/bind/named.conf.local
15.11.2012-12:07 - DEBUG - Processed datalog_id 2244
15.11.2012-12:07 - DEBUG - Calling function 'restartBind' from module 'dns_module'.
15.11.2012-12:07 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
finished.

And again nothing changed.

[till]

The file /etc/bind/pri.filerift.com is not there or does it still contain the old Ip address?

[todx]

File "/etc/bind/pri.filerift.com" exists and contains the old IP even when I manually run server.sh script in debug mode.

It seems that ISPC3 updates everything just fine except DNS records. It takes longer but in the end it updates the zone files but sometimes that takes a very long time.

Any ideas?

EDIT: ** Ok so I re-did my steps again and checked the pri.filerift.com file and it included the NEW IP address however when I ping filerift.com it shows the old IP address, could there be something wrong with bind9?

[till]

EDIT: ** Ok so I re-did my steps again and checked the pri.filerift.com file and it included the NEW IP address however when I ping filerift.com it shows the old IP address, could there be something wrong with bind9?

Pleasetest bidn with this command executed on the server:

dig@localhost filerift.com

In general: changes in dns like changing an IP address may take up to 48 hours, thats normal and does not depend on ispconfig. ISPConfig changes the IP within 60 seconds, but other dns servers are caching the dns record and they will not recognize the new IP address until the ttl of this dns record expired.

[todx]

Okay thanks till I think I got it. But don't DNS servers cache NS records only and not the entire DNS zone?

Will changing the ttl to a shorter time make any difference?

Lets take no-ip.com in consideration, they instantly update IPs allocated to sub-domains, any idea on how to achieve that?

[till]

Okay thanks till I think I got it. But don't DNS servers cache NS records only and not the entire DNS zone?

The records were cached, as a external server normally does not know which records exist in a zone.

Will changing the ttl to a shorter time make any difference?

Yes. But not all external servers will care about that.