server 127.0.0.1
zone ccnr.biotechnology.
update add second 86400 in cname first
send
update failed: NOTZONE
Have you tried specifying qualified names?
update add second.ccnr.biotechnology. 86400 in cname
first.ccnr.biotechnology.
-JP
sort of a false alarm
nsupdate with FQDN(dot) did work!(???)
On 17/05/12 12:03, lejeczek wrote:
hi everybody
when I do:
server 127.0.0.1
zone ccnr.biotechnology.
update add second 86400 in cname first
send
update failed: NOTZONE
in log I get:
May 17 11:59:10 whale named[2910]: debug
Our local university-wide recursive nameservers have
options { /* ... */
recursive-clients 5000;
}
This is meant to be reached only at very bad times indeed. During a recent
network partition incident, I noticed that named logged
named: general: error: socket: file descriptor exceeds
I've recently released a dlz ENUM module for the bind9 nameserver:
http://www.opentelecoms.org/dlz-ldap-enum
Basically, it handles ENUM queries from repro, FreeSWITCH, Kamailio,
Asterisk, Lumicall, etc, searches for the phone number in LDAP, and if
found, returns the email address as both a
4 matches
Mail list logo