arbitrary key names in named.conf

I've been using the key file name as key name in named.conf for simplicity, but I find that distros tend to use a default filename for a host key, so can I just use the key contents and assign it an arbitrary name in named.conf? -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http:

Re: connection timed out; no servers could be reached

On Sat, Mar 7, 2009 at 8:44 PM, Bill Landry wrote: > I have to admit that I am a bit baffled by this one.  I can query > against my bandwidth providers name servers (Comcast) and get name > resolution just fine for the hostname www.malware.com.br: Check firewall settings. Connection timed out is

connection timed out; no servers could be reached

Hi list, I have to admit that I am a bit baffled by this one. I can query against my bandwidth providers name servers (Comcast) and get name resolution just fine for the hostname www.malware.com.br: dig @68.87.78.130 www.malware.com.br +short server10.hiperlinks.com.br. 66.79.164.43 dig @68.87.

dnssec and sdb/dlz

I haven't found any documentation on this, but is it possible to implement dnssec/signed zones if the zone data exists in an sql db instead of a zone file? I know I can modify an sql table for a zone to have additional fields (for sdb use) for the additional RR types, but will the sdb interface re

Re: automatic resigning in 9.6.x

> Ok...so to implement this in bind 9.4.2-P2, I see the directive > sig-validity-interval in the ARM, if I set this to 1, > edit zone.db.signed, add a new entry, increment the serial, rndc > reload, what tells bind to resign the zone, and when? Using a dynamic zone, and sending an update. First o

Re: automatic resigning in 9.6.x

On Fri, Mar 6, 2009 at 11:46 PM, Evan Hunt wrote: > BIND 9 has, I believe, always had some support for automatic signing in the > case of zone updates--at least as far back as 9.3, and I haven't looked at > anything earlier.  Basically, if you have a signed zone and you insert a > new record, tha

Re: single-character host names

How about ; <<>> DiG 9.4.3b2 <<>> -t . @a.root-servers.net ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49774 ;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 14 ;; WARNING: recursion requested but not availab