Feature Request: name pools

Re: Feature Request: name pools

From:

Date:

Time:

I have one pet peave/suggestion if you do add an auto ptr deal...

I don't use any cnames, just A records. so if I go and do a 'create reverse records automatically' deal, it starts at 'a' and runs through all the domains adding new machines it didn't find in the 'a' names and so on. problem is, my domain is digitalspeed, but in ptr I end up with www.astudio.com. as reverse for my server :)

I would like a preference to create reverse records for 'primary domain only'
or better yet a checkbox to include each domain in a reverse list (or not).

It's a minor deal, but please don't forget that not all of us have 8000 machines and 1 domain, we might have 5 machines and 8000 domains :)

That said I think these are all good ideas.

/.02

-Aaron

>
> > >This is probably a proprietary feature; I know I haven't seen it in
> >>the RFCs (but I could have missed it):
> >>
> >>I would really like to be able to enter an IP range and have every
> >>reverse lookup on that range match a single name (or even random
> >>names based on a name pattern like "machineXX.nsd.org" where XX is a
> >>random string).
> >>
> >>Why? More and more sites will refuse to let you have access or
> >>download software (especially encryption software that is export
> >>restricted) unless they can do a reverse lookup to identify your
> >>domain. Making an entry for every one of the 8000 computers on our
> >>network is obviously a waste of time. Even something that
> >>automatically generates the tables is a pain because it will
> > >eventually require maintenance of some sort.
> >
> >Sounds like a Bad Idea.? Running a large network requires
> maintenance.
> >Period. I can only imagine the error reports generated by
> DNS Expert. :-)
>
> Depends on how it is implemented. As far as DNS Expert would know,
> there would be an entry for ever machine. I can see where doing that
> would be a major change to the server software, though, because you
> now have to intercept every request and answer from virtual tables
> instead of the actual files.
>
> >Why not include a feature to auto-update the PTR records,
> when the A record
> >is modified. Tie the PTR to the A record.
>
> Yes, a big improvement to the Admin package would suffice. For
> example, you could tie addresses together as a serially-generated
> range of A records to maintain the original pool and then it could
> auto-generate the PTR records when you tell it to update. I'm not
> sure it would require less development time, since big changes would
> be needed to the Admin interface to make it work well (like the
> ability to hide/show portions of the table that represent a pool of
> addresses) but it would avoid any server-side problems.
>
> Then they could tie DNS Expert into the admin package so it
> automatically does a review of the changes before they are
> implemented to detect potential errors...
>
> Jon
>
> ====================================================
> Jon Wiederspan jon@comvista.com
> http://www.comvista.com/
>
> Human Chaos Theory: Small children in a clean room
> can effect very large changes in the cleanliness of
> the room.
>
>

Sales:
888/4-DPOINT

Support:
858/452-3696