Hi,running latest upstream version first might save you some time, it’s this:named can create unrecoverable managed-keys.jnl file (#2895) · Issues · ISC Open Source Projects / BIND · GitLabgitlab.isc.orgOndrej--Ondřej Surý — ISC (He/Him)My working hours and your working hours may be different. Plea
Saw this at startup:
18:09:14.595420 IP (tos 0x0, ttl 57, id 35985, offset 0, flags [none], proto
UDP (17), length 1167)
192.58.128.30.53 > 24.116.100.90.53955: [udp sum ok] 64207*- q: DNSKEY? .
4/0/1 . DNSKEY, . DNSKEY, . DNSKEY, . RRSIG ar: . OPT UDPsize=1472 DO (1139)
18:09:14.597537 IP (
> On May 14, 2022, at 12:35 AM, Matus UHLAR - fantomas
> wrote:
>
> On 13.05.22 10:06, Philip Prindeville wrote:
>> After rebooting my OpenWRT router with Bind 9.18.1 yesterday, I started
>> seeing a lot of:
>>
>>
>> May 12 19:24:06 OpenWrt named[11061]: validating ./NS: no valid signature
Hi,
I notice that went Bind 9.18.7 comes up on OpenWRT, and I'm running it as a
local resolver, resolution initially doesn't work and I get a lot of noise in
/var/log/messages like:
Dec 27 17:27:12 OpenWrt named[13171]: validating org/DS: no valid signature
found
Dec 27 17:27:12 OpenWrt named[
First of all, it’s harder to help you if you don’t share the real domains, but
let’s suppose at least the rpz.local is real.
The maximum length is **255** including the label length for each label. I have
no idea where you got 256. Each label have maximum length of 63 bytes (not
63-64).
Now, y
Configuring my RPZ installation, the zone fails to load because some
register are "too long". The error in the logs is something like:
"""
dns_master_load: ../primarios/db.rpz.local:137146: ran out of space
"""
I did some tests and the zone load fails if records are longer than 243
characters.
6 matches
Mail list logo
