Karl Auer wrote: >> DHCP does DDNS. RADIUS doesn't. > > NASes may..
Based on RADIUS User-Names? This is dumb. The NAS should at *least* assign names based on a VSA. Using the User-Name is wrong. > Here's the full scoop then: This "NAS" is a tunnel broker. When you > bring up a tunnel, you get an endpoint allocated to you. The tunnel > broker then registers that address against your name in an appropriate > domain. If you are "fred", it will register "fred.domain" for you, with > an forward record mapping the name to the allocated address. It also > registers the allocated address in the appropriate reverse zone, with a > reverse record mapping the address to the name. Nice... but there's no reason to *rely* on the User-Name. > So I'm thinking turn off the broken functionality in the NAS, and let > the RADIUS server do the updates. It has all the information it needs > except the nameserver to talk to, which could be configured into this > hypothetical module or script. Exactly. For now, it's best to write a script. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
