You'll need libidn and libiconv.
IDN code is in the bind-9.x tarball in contrib/idn/idnkit-1.0-src
You need to include the --with-idn=yes and --with-iconv=yes options.
I recall having had to configure and build idn first, and then build
bind including the options in each.
Jeff R.
On Tue, 2013-
Interesting. Intentionally "poison" your own cache so your users aren't
inconvenienced by anothers misconfiguration. Not sure how you go about
doing that on box. Perhaps bigger brains on this list can say.
I have had occasion to forge answers locally as an immediate fix for
name resolution issues
Hmm, I see an A record using the same query:
[foo@dns1 ~]$ dig +dnssec extended.nau.edu a
; <<>> DiG 9.8.1 <<>> +dnssec extended.nau.edu a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13732
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITI
Notifys are sent by default for all loaded zones. They go only to the
nameservers listed in the zonefile unless overridden with 'also-notify'
statements in the zone clause in named.conf.
Notify behavior is also tunable using several named.conf options
statements.
I'd recommend checking the BIND9
The in-addr.arpa zone does not appear to be delegated to you. You'll
either need to get that done, or have Bell Canada do it.
dig +trace 80.115.25.70.in-addr.arpa
; <<>> DiG 9.4.3 <<>> +trace 80.115.25.70.in-addr.arpa
;; global options: printcmd
. 513811 IN NS i.
5 matches
Mail list logo