round-robin using cnames

[Kevin Darcy]

I provide the reverse records mostly as a convenience, but there are some
applications which actually rely on it, e.g. event management and network
management need to associate SNMP traps with the machines that are generating
them, given only an IP address. My system also uses reverse lookups as a database
consistency aid: e.g. if you go to add a new entry, but the IP address already
maps to some other name, then the add will fail.


- Kevin
Jesus Couto wrote:

> On Wed, 16 Aug 2000, Kevin Darcy wrote:
>
> > are exceptions to these generalities, of course). My homegrown maintenance
> > system here doesn't generate reverse records for multi-A-record names at all.
>
>         Interesting, cause I'm working on something like that, and I find
> it more difficult to think of all the checks needed to have only 1 PTR and
> be sure that every address with an associated name has a PTR (example, if
> you delete the name thats is the current PTR, system will have to check
> into all the domains to see if something else points to that address,
> choose or ask somebody to choose one, and add the PTR) than just adding a
> PTR for the address every time an A pointing to the ip is added.
>
>         Any particular reason why you did it that way? And, any
> "exception" worth mentioning that would make it necessary to choose
> between all the A the one that we "need"? (.rhosts, as some post in the
> list archives mention, doesnt seems very important to me right now, but I
> guess the double-lookup trick it and a lot of other software does its
> going to be the answer)
>
>         Thanks in advance
>
>                                         Jesus Couto F.