I have a resolver that is not resolving several domains. So far what I
found in logs is this message, repeated several times in the span of every
minute
*nssv named[38251]: resolver priming query complete: failure*
I'm using BIND 9.18.28
This is current config
# named-checkconf -p
options {
dire
Was wondering If would be possible to setup a forwarding scheme just for
some subdomains, I emphasize the fact that master is publicly accesible
and current need is to locally resolv a bunch of subdomains of the same
zone. I think image attached in previuos message is pretty explanatory,
but cu
NS ns2.dominio.edu.ar.
;; ADDITIONAL SECTION:
ns1.dominio.edu.ar. 3600IN A XXX.XXX.XXX.XXX
ns2.dominio.edu.ar. 3600IN A XXX.XXX.XXX.XXY
;; Query time: 33 msec
;; SERVER: XXX.XXX.XXX.XXX#53(XXX.XXX.XXX.XXX)
;; WHEN: lun ago 02 17:36:42 -03 2021
;; MSG SIZE
As of this morning I'm getting this error on log, and was working fine
previously
loading configuration from '/etc/bind/named.conf'
directory '/etc/bind' is not writable
/etc/bind/named.conf.options:2: parsing failed: permission denied
/etc/bind detail
drwxr-sr-x 4 root bind 4,0K jun 22 11:1
Before I start describing the problem, I should mention that this
incident started when I tried to enable DNSSEC. I understand that it is
unrelated, but previously everything was working correctly.
I'm using Debian 11 and Bind 9.18 from backports
This is current config
# named-checkconf -p
enter the directory.
Danilo
On 28.6.2023 20:44, Daniel Armando Rodriguez via bind-users wrote:
Before I start describing the problem, I should mention that this
incident started when I tried to enable DNSSEC. I understand that it
is unrelated, but previously everything was working correctly.
El 2023-06-28 16:00, Anand Buddhdev escribió:
On 28/06/2023 20:44, Daniel Armando Rodriguez via bind-users wrote:
Hi Daniel,
[snip]
# ls -alh /etc/bind/zonas/
drw-r-S--- 2 bind bind 4,0K jun 28 14:55 .
drwxr-sr-x 3 root bind 4,0K jun 28 15:06 ..
-rwxr-xr-- 1 bind bind 323 ene 16 10:59
However, as soon as I added this
dnssec-policy "default";
inline-signing yes;
Error came up again :-(
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us a
ermissions you had originally where wrong and wouldn’t normally
be that way.
Something or someone changed them. It may have happened again. We can’t see
what you see
so you have to show more details. If you you still have an error message
cut-and-paste the
new one including time stamps.
On
El 29/6/23 a las 09:40, Anand Buddhdev escribió:
On 29/06/2023 14:13, Daniel Armando Rodriguez via bind-users wrote:
[snip]
Error is not the same as before, I see it know (fresh eyes maybe)
Jun 29 08:42:37 web kernel: [5679658.761672] audit: type=1400
audit(1688038957.685:548): apparmor
escribió:
I suspect permissions on the key-directory are not yet correct:
key-directory "/var/cache/bind/keys";
On 6/28/23 22:35, Daniel Armando Rodriguez via bind-users wrote:
However, as soon as I added this
dnssec-policy "default";
inline-signing yes;
;
On 6/28/23 22:35, Daniel Armando Rodriguez via bind-users
wrote:
However, as soon as I added this
dnssec-policy "default";
inline-signing yes;
Error came up again :-(
Tot mails,
bind userlist m
12 matches
Mail list logo
