Re: [pfSense] Dynamic DNS force update?
Hi Martin. You've hit right on the problem. The IP is NOT different than the cached IP, thus the client will not update no matter what I do, even if I delete the entry entirely and re-create it (much less your simpler suggestion). My question very specifically was whether is it possible to force an update WITHOUT changing the interface address (i.e. without changing the address as a method of making the IP different than the cached IP) Does anyone know if it is possible? Should the client be tweaked to check the DNS host in addition to checking the cached value, or have something like a force update function? -Karl On 2/22/2012 6:14 AM, Fuchs, Martin wrote: Hi ! Try editing the dyndns-provider and just hit the save button J This should work, if the ip is different from the cached ip Regards, martin *Von:*list-boun...@lists.pfsense.org [mailto:list-boun...@lists.pfsense.org] *Im Auftrag von *Karl Fife *Gesendet:* Mittwoch, 22. Februar 2012 06:12 *An:* list@lists.pfsense.org *Betreff:* [pfSense] Dynamic DNS force update? Is there a way to force the Dynamic DNS client to post an update? It would appear that the only way to do this is to change the IP address bound to the montored interface. My question very specifically is, is it possible to force an update WITHOUT changing the interface address? I have a remote installation where I want to configure the DDNS client, and currently the DNS server currently has the WRONG address, so naturally I would like the correction to be performed by the DDNS client as a validation of the initial configuration. The problem is that the client will not post an update because it ONLY looks to see if the cached IP value on the interface has not changed. It does not (for example) look to the DNS host to see if there's a mismatch. Disabling/Enabling the client will NOT trigger an update because it still relies only on the cached value of the interface. DELETING and re-creating the client entry completely will also fail to trigger an update for the same reason. Obviously I can't release the remote WAN IP address from the interface because I would lose my connectivity. Is there a way to clear this cached value, or force an update? Maybe from the command line? Can I put in a plea to include a 'force update' button, in a future release, or preferably have the client just automatically dip the DNS host to check to see if there is an initial IP mismatch? At a minimum it seems this should happen at the creation of the client, perhaps also when settings are changed or when the client is bounced. If you have an urge to say Just go change the A record the first time, please sit on your hands. :-) Thanks! -K ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Dynamic DNS force update?
Change the cached number, then do as Martin Fuchs suggested. On Wed, 2012-02-22 at 10:02 -0600, Karl Fife wrote: Hi Martin. You've hit right on the problem. The IP is NOT different than the cached IP, thus the client will not update no matter what I do, even if I delete the entry entirely and re-create it (much less your simpler suggestion). My question very specifically was whether is it possible to force an update WITHOUT changing the interface address (i.e. without changing the address as a method of making the IP different than the cached IP) Does anyone know if it is possible? Should the client be tweaked to check the DNS host in addition to checking the cached value, or have something like a force update function? -Karl On 2/22/2012 6:14 AM, Fuchs, Martin wrote: Hi ! Try editing the dyndns-provider and just hit the save button J This should work, if the ip is different from the cached ip Regards, martin Von: list-boun...@lists.pfsense.org [mailto:list-boun...@lists.pfsense.org] Im Auftrag von Karl Fife Gesendet: Mittwoch, 22. Februar 2012 06:12 An: list@lists.pfsense.org Betreff: [pfSense] Dynamic DNS force update? Is there a way to force the Dynamic DNS client to post an update? It would appear that the only way to do this is to change the IP address bound to the montored interface. My question very specifically is, is it possible to force an update WITHOUT changing the interface address? I have a remote installation where I want to configure the DDNS client, and currently the DNS server currently has the WRONG address, so naturally I would like the correction to be performed by the DDNS client as a validation of the initial configuration. The problem is that the client will not post an update because it ONLY looks to see if the cached IP value on the interface has not changed. It does not (for example) look to the DNS host to see if there's a mismatch. Disabling/Enabling the client will NOT trigger an update because it still relies only on the cached value of the interface. DELETING and re-creating the client entry completely will also fail to trigger an update for the same reason. Obviously I can't release the remote WAN IP address from the interface because I would lose my connectivity. Is there a way to clear this cached value, or force an update? Maybe from the command line? Can I put in a plea to include a 'force update' button, in a future release, or preferably have the client just automatically dip the DNS host to check to see if there is an initial IP mismatch? At a minimum it seems this should happen at the creation of the client, perhaps also when settings are changed or when the client is bounced. If you have an urge to say Just go change the A record the first time, please sit on your hands. :-) Thanks! -K ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Dynamic DNS force update?
My question is of course, HOW. How does one change the cached number without releasing the address on the monitored interface? -K On 2/22/2012 11:47 AM, Bob Gustafson wrote: Change the cached number, then do as Martin Fuchs suggested. On Wed, 2012-02-22 at 10:02 -0600, Karl Fife wrote: Hi Martin. You've hit right on the problem. The IP is NOT different than the cached IP, thus the client will not update no matter what I do, even if I delete the entry entirely and re-create it (much less your simpler suggestion). My question very specifically was whether is it possible to force an update WITHOUT changing the interface address (i.e. without changing the address as a method of making the IP different than the cached IP) Does anyone know if it is possible? Should the client be tweaked to check the DNS host in addition to checking the cached value, or have something like a force update function? -Karl On 2/22/2012 6:14 AM, Fuchs, Martin wrote: Hi ! Try editing the dyndns-provider and just hit the save button J This should work, if the ip is different from the cached ip Regards, martin Von: list-boun...@lists.pfsense.org [mailto:list-boun...@lists.pfsense.org] Im Auftrag von Karl Fife Gesendet: Mittwoch, 22. Februar 2012 06:12 An: list@lists.pfsense.org Betreff: [pfSense] Dynamic DNS force update? Is there a way to force the Dynamic DNS client to post an update? It would appear that the only way to do this is to change the IP address bound to the montored interface. My question very specifically is, is it possible to force an update WITHOUT changing the interface address? I have a remote installation where I want to configure the DDNS client, and currently the DNS server currently has the WRONG address, so naturally I would like the correction to be performed by the DDNS client as a validation of the initial configuration. The problem is that the client will not post an update because it ONLY looks to see if the cached IP value on the interface has not changed. It does not (for example) look to the DNS host to see if there's a mismatch. Disabling/Enabling the client will NOT trigger an update because it still relies only on the cached value of the interface. DELETING and re-creating the client entry completely will also fail to trigger an update for the same reason. Obviously I can't release the remote WAN IP address from the interface because I would lose my connectivity. Is there a way to clear this cached value, or force an update? Maybe from the command line? Can I put in a plea to include a 'force update' button, in a future release, or preferably have the client just automatically dip the DNS host to check to see if there is an initial IP mismatch? At a minimum it seems this should happen at the creation of the client, perhaps also when settings are changed or when the client is bounced. If you have an urge to say Just go change the A record the first time, please sit on your hands. :-) Thanks! -K ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Dynamic DNS force update?
Hmm, must be stored somewhere. Check the source code. On Wed, 2012-02-22 at 12:06 -0600, Karl Fife wrote: My question is of course, HOW. How does one change the cached number without releasing the address on the monitored interface? -K On 2/22/2012 11:47 AM, Bob Gustafson wrote: Change the cached number, then do as Martin Fuchs suggested. On Wed, 2012-02-22 at 10:02 -0600, Karl Fife wrote: Hi Martin. You've hit right on the problem. The IP is NOT different than the cached IP, thus the client will not update no matter what I do, even if I delete the entry entirely and re-create it (much less your simpler suggestion). My question very specifically was whether is it possible to force an update WITHOUT changing the interface address (i.e. without changing the address as a method of making the IP different than the cached IP) Does anyone know if it is possible? Should the client be tweaked to check the DNS host in addition to checking the cached value, or have something like a force update function? -Karl On 2/22/2012 6:14 AM, Fuchs, Martin wrote: Hi ! Try editing the dyndns-provider and just hit the save button J This should work, if the ip is different from the cached ip Regards, martin Von: list-boun...@lists.pfsense.org [mailto:list-boun...@lists.pfsense.org] Im Auftrag von Karl Fife Gesendet: Mittwoch, 22. Februar 2012 06:12 An: list@lists.pfsense.org Betreff: [pfSense] Dynamic DNS force update? Is there a way to force the Dynamic DNS client to post an update? It would appear that the only way to do this is to change the IP address bound to the montored interface. My question very specifically is, is it possible to force an update WITHOUT changing the interface address? I have a remote installation where I want to configure the DDNS client, and currently the DNS server currently has the WRONG address, so naturally I would like the correction to be performed by the DDNS client as a validation of the initial configuration. The problem is that the client will not post an update because it ONLY looks to see if the cached IP value on the interface has not changed. It does not (for example) look to the DNS host to see if there's a mismatch. Disabling/Enabling the client will NOT trigger an update because it still relies only on the cached value of the interface. DELETING and re-creating the client entry completely will also fail to trigger an update for the same reason. Obviously I can't release the remote WAN IP address from the interface because I would lose my connectivity. Is there a way to clear this cached value, or force an update? Maybe from the command line? Can I put in a plea to include a 'force update' button, in a future release, or preferably have the client just automatically dip the DNS host to check to see if there is an initial IP mismatch? At a minimum it seems this should happen at the creation of the client, perhaps also when settings are changed or when the client is bounced. If you have an urge to say Just go change the A record the first time, please sit on your hands. :-) Thanks! -K ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Dynamic DNS force update?
Am 22.02.2012 19:06, schrieb Karl Fife: My question is of course, HOW. How does one change the cached number without releasing the address on the monitored interface? -K Have a look at the files matching /conf/dyndns* and try editing those. -Stefan ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Dynamic DNS force update?
The file: /cf/conf/dyndns_wanzoneedit'my.domain.net'.cache Indeed contains the cached IP address, but the file system is mounted read-only. I assume this is due to the fact that I am running the embedded version. I'm starting to think that the answer is an unqualified NO. -K On 2/22/2012 1:28 PM, newsgroups.ma...@stefanbaur.de wrote: Am 22.02.2012 19:06, schrieb Karl Fife: My question is of course, HOW. How does one change the cached number without releasing the address on the monitored interface? -K Have a look at the files matching /conf/dyndns* and try editing those. -Stefan ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Dynamic DNS force update?
On Wed, Feb 22, 2012 at 6:03 PM, Karl Fife karlf...@gmail.com wrote: The file: /cf/conf/dyndns_wanzoneedit'my**.domain.net http://my.domain.net'.cache Indeed contains the cached IP address, but the file system is mounted read-only. I assume this is due to the fact that I am running the embedded version. I'm starting to think that the answer is an unqualified NO. Just saw your message. The answer is (as I wrote in my other recent post to this thread) that it is supposed to work (there is a secret way to mount the config in write-mode), but it is a minor bug. I plan to submit a patch tonight. - Y ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Dynamic DNS force update?
See also http://redmine.pfsense.org/issues/2166 On Wed, 2012-02-22 at 18:20 -0500, Yehuda Katz wrote: On Wed, Feb 22, 2012 at 2:20 PM, Yehuda Katz yeh...@ymkatz.net wrote: On Wed, Feb 22, 2012 at 11:02 AM, Karl Fife karlf...@gmail.com wrote: My question very specifically was whether is it possible to force an update WITHOUT changing the interface address (i.e. without changing the address as a method of making the IP different than the cached IP) Does anyone know if it is possible? Should the client be tweaked to check the DNS host in addition to checking the cached value, or have something like a force update function? I am looking at the feasibility of adding this feature myself. It may take me until next week due to my school work (I am a full time college student). Turns out that there is a bug in the update code. The cache filenames are not always generated the same way. See this redmine bug: http://redmine.pfsense.org/issues/2228 ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
