Hi ?
You have delegated the domain "sub.test.local" but you have no zone
statement for this zone.
Suggest you create a db.sub.test.local zone file and update your
configuration with
zone "sub.test.local" IN {
type master;
file "db.sub.test.local";
};
Hi Brett,
./configure -h
Will give you list of the available options.
Peter
On 23/12/2019 06:38, Brett Delmage wrote:
> I'm building bind-9.15.7 on Ubuntu 18.04, so I can try some of the
> newest features.
>
> I have never built bind before. I configured and compiled using the
> default options
Hi Patrik,
192.168.81.20 appears to be matched to the internal-enp1s0f3 view.
This view might not be able to resolve these external dns entries correctly
what do you get when you try
dig @192.168.81.20 com soa
and
dig @192.168.81.20 production.cloudflare.docker.com +trace
Kind Regards Peter
Hi Patrik,
I don't see any SERVFAIL querying for this record. maybe
your"internal-enp1s0f3" view is configured to bump this domain?
Kind Regards Peter
dig aax-eu.amazon-adsystem.com
; <<>> DiG 9.10.2-P4 <<>> aax-eu.amazon-adsystem.com
;; global options: +cmd
;; Got answer:
;;
Re: Bind 9.9.13rc1
I note that the "--enable-dnstap" options has been removed.
Is dnstap now enabled by default?
Thanks in advance Peter
Forwarded Message
Subject: New BIND release candidates are available: 9.9.13rc1,
9.10.8rc1, 9.11.4rc1, 9.12.2rc1, and 9.13.1
Date:
Hi Blason,
My understanding is that if there is no "notify no;" statement, then
bind will send notifies to all name servers for a given zone.
Also notify pertains too the notification of name servers not included
in zone data.
Kind Regards Peter
On 04/05/2018 05:51, Blason R wrote:
Hi,
6 matches
Mail list logo
