Re: DNS zone transfer module
On Apr 24, 2006, at 9:31 AM, Chris wrote: I created a module that extends Net::DNS::Resolver to make zone transfers a little easier. It looks up the nameserver records for a zone, and then performs transfers from each nameserver until it gets a response. SYNOSIS use Net::DNS; use Net::DNS::Resolver::ForceAxfer; I think force might be too strong a word here. It's really just trying very hard or something. Maybe Net::DNS::Resolver::TransferKit or something? In general I try to stay away from verbs (and verb-ified nouns, like Forcer) in module names. What if you want to add another capability, do you add another verb? =) -Ken
Re: DNS zone transfer module
A. Pagaltzis wrote: Maybe ForceAXfer? I only have a superficial knowledge of the DNS protocol, but I assume that the “A” refers to A records and the “xfer” part is a separate word. Is that right? If so, treating them as separate words would look better. Since the opcode is AXFR (no e), shouldn't it be ForceAXFR or ForceAxfr? And I agree that method names should be lowercase with underscores. -- Keith C. Ivey [EMAIL PROTECTED] Washington, DC
Re: DNS zone transfer module
On Mon, 24 Apr 2006, Keith Ivey wrote: Since the opcode is AXFR (no e), shouldn't it be ForceAXFR or ForceAxfr? And I agree that method names should be lowercase with underscores. I'd agree to change the method to direct_axfr (based on KW's earlier message), and use the underscore method in this case, since the other methods of Net::DNS::Resolver use the underscore format. -- Keith C. Ivey [EMAIL PROTECTED] Washington, DC Christopher Josephes [EMAIL PROTECTED]
Unresponsive? How about dead?
I know there is a FAQ about module authors who are unresponsive. But I'm talking about one who is unresponsive, and his e-mail addresses all bounce, and his website is gone, and, well, I fear for the worst. Insert Monty Python Dead Parrot Sketch references here. Anyway, if someone is unresponsive and never coming back, what do we do then?
Re: Unresponsive? How about dead?
On 4/25/06, Steve Vance [EMAIL PROTECTED] wrote: I know there is a FAQ about module authors who are unresponsive. But I'm talking about one who is unresponsive, and his e-mail addresses all bounce, and his website is gone, and, well, I fear for the worst. Insert Monty Python Dead Parrot Sketch references here. Anyway, if someone is unresponsive and never coming back, what do we do then? maintain their modules without them and prefix their names with memorial underscores -- David L Nicol Document what you do, then do what you documented
Re: DNS zone transfer module
On Tue, 25 Apr 2006, Ken Williams wrote: I think force might be too strong a word here. It's really just trying very hard or something. Maybe Net::DNS::Resolver::TransferKit or something? In general I try to stay away from verbs (and verb-ified nouns, like Forcer) in module names. What if you want to add another capability, do you add another verb? =) Good point. How about Net::DNS::Resolver::DirectAxfer. Or maybe something more friendly like DirectTransfer. Christopher Josephes [EMAIL PROTECTED]
Re: DNS zone transfer module
On Tue, 25 Apr 2006, David Golden wrote: Given that, why not just: * Net::DNS::AXFR That's pretty obviously a tool for doing DNS AXFR. If there's a specific feature that it provides (i.e. direct), just tack that on as a more specific qualifier: Well, the code won't work at all without Net::DNS::Resolver, so I don't want to mistakenly present it as a standalone client. I thought making a DNS client module exclusively for zone transfers to be a little over the top. I think the best suggestion so far has been Net::DNS::Resolver::DirectAxfr, which I'm leaning towards. Christopher Josephes [EMAIL PROTECTED]
