I think you are correct. RFC 2136 seems to be focused on the server
rather than the query client.

On Wed, 2012-02-22 at 17:39 -0600, Bob Gustafson wrote:
> It appears as though the DDNS is not updating properly, might be useful
> information.
> 
> Johan Braeken says:
>         Observed behaviour:
>         
>         When the IP address on the WAN interface changes, nothing
>         happens.
>         There is also nothing logged regarding Dynamic DNS updates.
>         
>         Expected behaviour:
>         
>         DNS server should be updated.
>         
>         Extra information:
>         
>         1: DNS server updates work when the RFC 2136 configuration is
>         opened and saved.
>         2: When in addition to the RFC 2136 entry a "dummy entry" is
>         made under the "DynDNS"-tab, the RFC 2136 configuration is also
>         working upon IP changes.
>         
>         I suspect there is somewhere a check to see if Dynamic DNS is
>         configured when the IP address changes, but the RFC 2136
>         configuration is not taken into account.
>         
> On Wed, 2012-02-22 at 18:33 -0500, Yehuda Katz wrote:
> > I do not have a RFC 2136 DNS setup to debug this with.
> > It is probably not related because the DynDNS and RFC 2136 features
> > are basically completely separate.
> > 
> > 
> > - Y
> > 
> > 
> > On Wed, Feb 22, 2012 at 6:29 PM, Bob Gustafson <[email protected]> wrote:
> >         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
> >         <[email protected]>
> >         > wrote:
> >         >         On Wed, Feb 22, 2012 at 11:02 AM, Karl Fife
> >         >         <[email protected]> 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
> >         > [email protected]
> >         > http://lists.pfsense.org/mailman/listinfo/list
> >         
> >         
> >         _______________________________________________
> >         List mailing list
> >         [email protected]
> >         http://lists.pfsense.org/mailman/listinfo/list
> >         
> > 
> > 
> > _______________________________________________
> > List mailing list
> > [email protected]
> > http://lists.pfsense.org/mailman/listinfo/list
> 
> 
> _______________________________________________
> List mailing list
> [email protected]
> http://lists.pfsense.org/mailman/listinfo/list


_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to