Tracy Reed wrote: ***SNIP***
> But having learned from the past I am very afraid of taking on any > such cleanup because that A record which everyone agrees isn't used > anymore actually serves some hidden critical function. Indeed. > > I am wondering if there are any tools out there which can make this > easier. For example I am thinking that if I had a way to capture a > month's worth of DNS traffic and then replay that against the new name > server and make sure that any queries which returned responses on the > old setup also returned the same responses on the new server that > would make things much better. > > Does such a tool exist? Is this a good idea? Any better way? > > If it doesn't exist and I don't come up with a better way I may just > whip it up myself. Wireshark to record plus some code to extract the > queries and responses plus some code to re-run them should do the > trick. I would grab all the DNS query logs for a week or more and run those through perl/awk/whatever to produce a list of names and record types that need to be queried. Then I would script (perl, sh, python whatever) to use dig or the equiv Perl or Python module to replay all the queries that were produced from the logs, *against* the original servers. Then I would do the same queries against the new servers. When the results agree, then you can cutover to the new servers. _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
