This happened again during this week's reload:

Feb 27 03:26:47 server.example.com named-pkcs11[1593328]: received control 
channel command 'reload'
Feb 27 03:26:48 server.example.com named-pkcs11[1593328]: zone 
22.75.10.in-addr.arpa/IN: shutting down
Feb 27 03:26:48 server.example.com named-pkcs11[1593328]: zone 
0.8.10.in-addr.arpa/IN: shutting down
Feb 27 03:26:48 server.example.com named-pkcs11[1593328]: zone 
101.168.192.in-addr.arpa/IN: shutting down
Feb 27 03:26:48 server.example.com named-pkcs11[1593328]: zone 
a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN: shutting down
Feb 27 03:26:50 server.example.com named-pkcs11[1593328]: zone 
3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa/IN: shutting down
Feb 27 03:26:50 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa/IN: shutting down
Feb 27 03:26:50 server.example.com named-pkcs11[1593328]: zone 
0.0.7.1.0.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: shutting down
Feb 27 03:26:51 server.example.com named-pkcs11[1593328]: zone 
0.0.6.d.1.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: shutting down
Feb 27 03:26:51 server.example.com named-pkcs11[1593328]: zone 
0.0.9.2.3.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: shutting down
Feb 27 03:26:52 server.example.com named-pkcs11[1593328]: zone 
2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN: shutting down
Feb 27 03:26:52 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.f.d.8.4.1.b.e.a.1.3.d.f.ip6.arpa/IN: shutting down
Feb 27 03:26:52 server.example.com named-pkcs11[1593328]: zone 
2.6.5.c.c.9.2.c.4.0.6.5.c.8.d.f.ip6.arpa/IN: shutting down
Feb 27 03:26:52 server.example.com named-pkcs11[1593328]: checkhints: unable to 
get root NS rrset from cache: not found
Feb 27 03:26:53 server.example.com named-pkcs11[1593328]: zone example.com/IN: 
shutting down
Feb 27 03:26:53 server.example.com named-pkcs11[1593328]: zone 
rbl.example.com/IN: shutting down
Feb 27 03:26:53 server.example.com named-pkcs11[1593328]: zone joip.com/IN: 
shutting down
Feb 27 03:26:53 server.example.com named-pkcs11[1593328]: checkhints: unable to 
get root NS rrset from cache: not found
Feb 27 03:29:54 server.example.com named-pkcs11[1593328]: loading configuration 
from '/etc/named.conf'
Feb 27 03:29:54 server.example.com named-pkcs11[1593328]: unable to open 
'/etc/bind.keys'; using built-in keys instead
Feb 27 03:29:54 server.example.com named-pkcs11[1593328]: looking for GeoIP2 
databases in '/usr/share/GeoIP'
Feb 27 03:29:54 server.example.com named-pkcs11[1593328]: opened GeoIP2 
database '/usr/share/GeoIP/GeoLite2-Country.mmdb'
Feb 27 03:29:54 server.example.com named-pkcs11[1593328]: opened GeoIP2 
database '/usr/share/GeoIP/GeoLite2-City.mmdb'
Feb 27 03:29:54 server.example.com named-pkcs11[1593328]: using default 
UDP/IPv4 port range: [32768, 60999]
Feb 27 03:29:54 server.example.com named-pkcs11[1593328]: using default 
UDP/IPv6 port range: [32768, 60999]
Feb 27 03:29:54 server.example.com named-pkcs11[1593328]: sizing zone task pool 
based on 13 zones
Feb 27 03:29:55 server.example.com named-pkcs11[1593328]: none:105: 
'max-cache-size 90%' - setting to 6889MB (out of 7654MB)
Feb 27 03:29:55 server.example.com named-pkcs11[1593328]: dns64 reverse zone: 
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.9.f.f.4.6.0.0.ip6.arpa.
Feb 27 03:30:04 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:04 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:04 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:04 server.example.com named-pkcs11[1593328]: GSSAPI client step 2
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: GSSAPI client step 2
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
10.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
16.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
17.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
18.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
19.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
20.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
21.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
22.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
23.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
24.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
25.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
26.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
27.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
28.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
29.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
30.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
31.172.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
168.192.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
64.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
65.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
66.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
67.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
68.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
69.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
70.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
71.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
72.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
73.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
74.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
75.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
76.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
77.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
78.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
79.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
80.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
81.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
82.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
83.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
84.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
85.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
86.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
87.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
88.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
89.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
90.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
91.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
92.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
93.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
94.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
95.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
96.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
97.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
98.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
99.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
100.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
101.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
102.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
103.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
104.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
105.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
106.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
107.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
108.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
109.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
110.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
111.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
112.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
113.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
114.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
115.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
116.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
117.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
118.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
119.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
120.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
121.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
122.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
123.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
124.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
125.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
126.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
127.100.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
127.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
254.169.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
2.0.192.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
100.51.198.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
113.0.203.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
255.255.255.255.IN-ADDR.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
D.F.IP6.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
8.E.F.IP6.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
9.E.F.IP6.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
A.E.F.IP6.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
B.E.F.IP6.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
8.B.D.0.1.0.0.2.IP6.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
EMPTY.AS112.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: automatic empty zone: 
HOME.ARPA
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: none:105: 
'max-cache-size 90%' - setting to 6889MB (out of 7654MB)
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: configuring command 
channel from '/etc/rndc.key'
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: configuring command 
channel from '/etc/rndc.key'
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.9.f.f.4.6.0.0.ip6.arpa/IN: (master) removed
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: reloading 
configuration succeeded
Feb 27 03:30:05 server.example.com named-pkcs11[1593328]: reloading zones 
succeeded
Feb 27 03:30:30 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:30 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:30 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:30 server.example.com named-pkcs11[1593328]: GSSAPI client step 2
Feb 27 03:30:30 server.example.com named-pkcs11[1593328]: managed-keys-zone: 
Unable to fetch DNSKEY set '.': timed out
Feb 27 03:30:31 server.example.com ns-slapd[1840]: 
[27/Feb/2022:03:30:31.170416667 -0500] - NOTICE - ldbm_back_search - Unindexed 
search: search base="cn=dns,dc=example,dc=com" scope=2 
filter="(|(objectClass=idnsConfigObject)(&(objectClass=idnsServerConfigObject)(idnsServerId=server.example.com))(|(objectClass=idnsZone)(objectClass=idnsForwardZone)(objectClass=idnsRecord)))"
 conn=15415 op=3
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: received control 
channel command 'reload'
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: loading configuration 
from '/etc/named.conf'
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: unable to open 
'/etc/bind.keys'; using built-in keys instead
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: looking for GeoIP2 
databases in '/usr/share/GeoIP'
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: opened GeoIP2 
database '/usr/share/GeoIP/GeoLite2-Country.mmdb'
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: opened GeoIP2 
database '/usr/share/GeoIP/GeoLite2-City.mmdb'
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: using default 
UDP/IPv4 port range: [32768, 60999]
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: using default 
UDP/IPv6 port range: [32768, 60999]
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: sizing zone task pool 
based on 13 zones
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: none:105: 
'max-cache-size 90%' - setting to 6889MB (out of 7654MB)
Feb 27 03:30:31 server.example.com named-pkcs11[1593328]: dns64 reverse zone: 
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.9.f.f.4.6.0.0.ip6.arpa.
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: GSSAPI client step 2
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: GSSAPI client step 2
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
10.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
16.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
17.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
18.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
19.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
20.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
21.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
22.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
23.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
24.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
25.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
26.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
27.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
28.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
29.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
30.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
31.172.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
168.192.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
64.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
65.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
66.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
67.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
68.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
69.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
70.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
71.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
72.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
73.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
74.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
75.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
76.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
77.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
78.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
79.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
80.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
81.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
82.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
83.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
84.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
85.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
86.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
87.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
88.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
89.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
90.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
91.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
92.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
93.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
94.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
95.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
96.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
97.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
98.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
99.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
100.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
101.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
102.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
103.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
104.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
105.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
106.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
107.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
108.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
109.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
110.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
111.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
112.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
113.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
114.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
115.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
116.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
117.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
118.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
119.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
120.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
121.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
122.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
123.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
124.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
125.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
126.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
127.100.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
127.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
254.169.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
2.0.192.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
100.51.198.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
113.0.203.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
255.255.255.255.IN-ADDR.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
D.F.IP6.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
8.E.F.IP6.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
9.E.F.IP6.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
A.E.F.IP6.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
B.E.F.IP6.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
8.B.D.0.1.0.0.2.IP6.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
EMPTY.AS112.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: automatic empty zone: 
HOME.ARPA
Feb 27 03:30:40 server.example.com named-pkcs11[1593328]: none:105: 
'max-cache-size 90%' - setting to 6889MB (out of 7654MB)
Feb 27 03:30:45 server.example.com named-pkcs11[1593328]: configuring command 
channel from '/etc/rndc.key'
Feb 27 03:30:45 server.example.com named-pkcs11[1593328]: configuring command 
channel from '/etc/rndc.key'
Feb 27 03:30:45 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.9.f.f.4.6.0.0.ip6.arpa/IN: (master) removed
Feb 27 03:30:45 server.example.com named-pkcs11[1593328]: reloading 
configuration succeeded
Feb 27 03:30:45 server.example.com named-pkcs11[1593328]: reloading zones 
succeeded
Feb 27 03:30:45 server.example.com named-pkcs11[1593328]: all zones loaded
Feb 27 03:30:45 server.example.com named-pkcs11[1593328]: running
Feb 27 03:30:46 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:46 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:46 server.example.com named-pkcs11[1593328]: GSSAPI client step 1
Feb 27 03:30:46 server.example.com named-pkcs11[1593328]: GSSAPI client step 2
Feb 27 03:30:46 server.example.com ns-slapd[1840]: 
[27/Feb/2022:03:30:46.365640747 -0500] - NOTICE - ldbm_back_search - Unindexed 
search: search base="cn=dns,dc=example,dc=com" scope=2 
filter="(|(objectClass=idnsConfigObject)(&(objectClass=idnsServerConfigObject)(idnsServerId=server.example.com))(|(objectClass=idnsZone)(objectClass=idnsForwardZone)(objectClass=idnsRecord)))"
 conn=15418 op=3
Feb 27 03:30:46 server.example.com named-pkcs11[1593328]: all zones loaded
Feb 27 03:30:46 server.example.com named-pkcs11[1593328]: running
Feb 27 03:30:46 server.example.com named-pkcs11[1593328]: managed-keys-zone: 
Key 20326 for zone . acceptance timer complete: key now trusted
Feb 27 03:30:47 server.example.com named-pkcs11[1593328]: checkhints: unable to 
get root NS rrset from cache: not found
Feb 27 03:30:50 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=example.com.,cn=dns,dc=example,dc=com 
fa486b2d-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 03:30:50 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2864
Feb 27 03:30:50 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=0.0.0.0.f.d.8.4.1.b.e.a.1.3.d.f.ip6.arpa.,cn=dns,dc=example,dc=com 
fa486b31-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 03:30:51 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2865
Feb 27 03:30:52 server.example.com named-pkcs11[1593328]: checkhints: unable to 
get root NS rrset from cache: not found
Feb 27 03:30:52 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa.,cn=dns,dc=example,dc=com 
fa486b33-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 03:30:52 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2866
Feb 27 03:30:52 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=0.0.0.0.3.d.5.d.1.c.3.4.2.0.0.2.ip6.arpa.,cn=dns,dc=example,dc=com 
fa486b35-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 03:30:52 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2867
Feb 27 03:30:54 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=22.75.10.in-addr.arpa.,cn=dns,dc=example,dc=com 
fa486b37-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 03:30:54 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2868
Feb 27 03:30:55 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=0.8.10.in-addr.arpa.,cn=dns,dc=example,dc=com 
43bdb682-3ed9-11e5-b0d0-8e21c4e9261b
Feb 27 03:30:55 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2869
Feb 27 03:30:56 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa.,cn=dns,dc=example,dc=com 
1ed0b809-82fd-11e5-93a0-8e21c4e9261b
Feb 27 03:30:56 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2870
Feb 27 03:30:56 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=joip.com.,cn=dns,dc=example,dc=com d0d05586-f36c-11e5-8ec6-8e21c4e9261b
Feb 27 03:30:56 server.example.com named-pkcs11[1593328]: zone 
10.IN-ADDR.ARPA/IN: shutting down
Feb 27 03:30:57 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2871
Feb 27 03:30:57 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=0.0.7.1.0.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa.,cn=dns,dc=example,dc=com 
86728702-c388-11e6-bbce-8e21c4e9261b
Feb 27 03:30:57 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2872
Feb 27 03:30:57 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=101.168.192.in-addr.arpa.,cn=dns,dc=example,dc=com 
59274702-eebf-11e7-82b4-8e21c4e9261b
Feb 27 03:30:57 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2873
Feb 27 03:30:57 server.example.com named-pkcs11[1593328]: checkhints: unable to 
get root NS rrset from cache: not found
Feb 27 03:30:58 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=rbl.example.com.,cn=dns,dc=example,dc=com 
9d5d0506-4c6f-11e8-be06-8e21c4e9261b
Feb 27 03:30:58 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2874
Feb 27 03:30:58 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=0.0.9.2.3.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa.,cn=dns,dc=example,dc=com 
c5593001-c8c1-11e8-a42f-8e21c4e9261b
Feb 27 03:30:58 server.example.com named-pkcs11[1593328]: checkhints: unable to 
get root NS rrset from cache: not found
Feb 27 03:30:58 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2875
Feb 27 03:30:58 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=0.0.6.d.1.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa.,cn=dns,dc=example,dc=com 
b33bcc01-08c9-11e9-803d-8e21c4e9261b
Feb 27 03:30:58 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2876
Feb 27 03:30:59 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=2.6.5.c.c.9.2.c.4.0.6.5.c.8.d.f.ip6.arpa.,cn=dns,dc=example,dc=com 
79072a01-112b-11ea-b32b-8e21c4e9261b
Feb 27 03:30:59 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2877
Feb 27 03:31:00 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=0.0.0.0.3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa.,cn=dns,dc=example,dc=com 
e3beaa01-ce24-11eb-8263-8e21c4e9261b
Feb 27 03:31:00 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2878
Feb 27 03:39:01 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 03:39:01 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 03:39:01 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 03:39:01 server.example.com sssd_be[2295076]: GSSAPI client step 2
Feb 27 03:46:55 server.example.com named-pkcs11[1593328]: client 
@0x7f9a37dd9a50 140.238.153.74#42321 (a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa): 
bad zone transfer request: 'a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN': 
non-authoritative zone (NOTAUTH)
Feb 27 03:46:55 server.example.com named-pkcs11[1593328]: client 
@0x7f9a477be700 fd8c:5604:c29c:c562::1001#53623 
(a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa): bad zone transfer request: 
'a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 03:49:32 server.example.com named-pkcs11[1593328]: client 
@0x7f9a48cb1260 140.238.153.74#45809 
(2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa): bad zone transfer request: 
'2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 03:49:33 server.example.com named-pkcs11[1593328]: client 
@0x7f9a3f6ba820 fd8c:5604:c29c:c562::1001#54249 
(2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa): bad zone transfer request: 
'2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 03:51:29 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:51:29 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21a1/info
Feb 27 03:51:29 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:51:29 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21a1/info
Feb 27 03:51:29 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:51:29 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21a3/info
Feb 27 03:51:29 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:51:29 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21a5/info
Feb 27 03:54:06 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 03:54:06 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 03:54:06 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 03:54:06 server.example.com sssd_be[2295076]: GSSAPI client step 2
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21a7/info
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21a7/info
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21a7/info
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21a9/info
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 03:54:24 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21ab/info
Feb 27 03:59:24 server.example.com named-pkcs11[1593328]: client 
@0x7f9a48be9820 140.238.153.74#60207 (a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa): 
bad zone transfer request: 'a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN': 
non-authoritative zone (NOTAUTH)
Feb 27 03:59:24 server.example.com named-pkcs11[1593328]: client 
@0x7f9a3e566890 fd8c:5604:c29c:c562::1001#40605 
(a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa): bad zone transfer request: 
'a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21ad/info
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21ad/info
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21af/info
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21af/info
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:00:02 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21b1/info
Feb 27 04:00:49 server.example.com named-pkcs11[1593328]: client 
@0x7f9a5ff03de0 140.238.153.74#57787 
(2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa): bad zone transfer request: 
'2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 04:00:49 server.example.com named-pkcs11[1593328]: client 
@0x7f9a3711f4f0 fd8c:5604:c29c:c562::1001#51587 
(2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa): bad zone transfer request: 
'2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 04:02:08 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:02:08 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21b3/info
Feb 27 04:02:08 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:02:08 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21b3/info
Feb 27 04:02:08 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:02:08 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21b5/info
Feb 27 04:02:08 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:02:08 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21b7/info
Feb 27 04:03:15 server.example.com tls_prune[2956111]: tls_prune: purged 376 
out of 802 entries
Feb 27 04:05:09 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:05:09 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21b9/info
Feb 27 04:05:09 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:05:09 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21b9/info
Feb 27 04:05:09 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:05:09 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21bb/info
Feb 27 04:05:09 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:05:09 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21bd/info
Feb 27 04:09:06 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 04:09:06 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 04:09:06 server.example.com sssd_be[2295076]: GSSAPI client step 1
Feb 27 04:09:06 server.example.com sssd_be[2295076]: GSSAPI client step 2
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21bf/info
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21bf/info
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21bf/info
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21c1/info
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21c1/info
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:11:05 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21c3/info
Feb 27 04:12:27 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:12:27 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21c5/info
Feb 27 04:12:27 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:12:27 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21c7/info
Feb 27 04:12:27 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:12:27 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21c9/info
Feb 27 04:13:03 server.example.com named-pkcs11[1593328]: client 
@0x7f9a5c5a4920 140.238.153.74#44765 (a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa): 
bad zone transfer request: 'a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN': 
non-authoritative zone (NOTAUTH)
Feb 27 04:13:03 server.example.com named-pkcs11[1593328]: client 
@0x7f9a3c6811e0 fd8c:5604:c29c:c562::1001#56213 
(a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa): bad zone transfer request: 
'a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 04:13:32 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:13:32 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21cb/info
Feb 27 04:13:32 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:13:32 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21cb/info
Feb 27 04:13:32 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:13:32 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21cd/info
Feb 27 04:13:32 server.example.com rpc.gssd[1849]: ERROR: unable to resolve 
2001:123:aa:123:0:90cc:a629:cf42:5877 to hostname: Name or service not known
Feb 27 04:13:32 server.example.com rpc.gssd[1849]: ERROR: failed to parse 
nfs/clnt21cf/info
Feb 27 04:14:03 server.example.com named-pkcs11[1593328]: client 
@0x7f9a353e53b0 140.238.153.74#58363 
(2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa): bad zone transfer request: 
'2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 04:14:04 server.example.com named-pkcs11[1593328]: client 
@0x7f9a3703be70 fd8c:5604:c29c:c562::1001#34319 
(2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa): bad zone transfer request: 
'2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN': non-authoritative zone (NOTAUTH)
Feb 27 04:14:34 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:34.750220972 -0500] - ERR - _entry_set_tombstone_rdn - 
Failed to convert DN cn=KDC to RDN
Feb 27 04:14:34 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:34.855281321 -0500] - ERR - id2entry - str2entry returned 
NULL for id 134196, string="rdn"
Feb 27 04:14:34 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:34.888698455 -0500] - ERR - _entry_set_tombstone_rdn - 
Failed to convert DN cn=KPASSWD to RDN
Feb 27 04:14:34 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:34.921982158 -0500] - ERR - id2entry - str2entry returned 
NULL for id 134197, string="rdn"
Feb 27 04:14:34 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:34.955551334 -0500] - ERR - _entry_set_tombstone_rdn - 
Failed to convert DN cn=HTTP to RDN
Feb 27 04:14:34 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:34.988859492 -0500] - ERR - id2entry - str2entry returned 
NULL for id 134198, string="rdn"
Feb 27 04:14:35 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:35.022312939 -0500] - ERR - _entry_set_tombstone_rdn - 
Failed to convert DN cn=OTPD to RDN
Feb 27 04:14:35 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:35.080766013 -0500] - ERR - id2entry - str2entry returned 
NULL for id 134199, string="rdn"
Feb 27 04:14:35 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:35.122619035 -0500] - ERR - _entry_set_tombstone_rdn - 
Failed to convert DN cn=KEYS to RDN
Feb 27 04:14:35 server.example.com ns-slapd[1840]: 
[27/Feb/2022:04:14:35.164290434 -0500] - ERR - id2entry - str2entry returned 
NULL for id 134200, string="rdn"
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
22.75.10.in-addr.arpa/IN: loaded serial 1645950653
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.8.10.in-addr.arpa/IN: loaded serial 1645950654
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
101.168.192.in-addr.arpa/IN: loaded serial 1645950657
Feb 27 04:14:36 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa.,cn=dns,dc=example,dc=com 
8d1f2201-91a2-11ec-88b1-dfbaae19c7b5
Feb 27 04:14:36 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2879
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN: loaded serial 1645950650
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa/IN: loaded serial 1645953275
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa/IN: loaded serial 1645950660
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.7.1.0.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: loaded serial 1645950656
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.6.d.1.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: loaded serial 1645950658
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.9.2.3.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: loaded serial 1645950658
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN: loaded serial 1645950655
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
22.75.10.in-addr.arpa/IN: sending notifies (serial 1645950653)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.f.d.8.4.1.b.e.a.1.3.d.f.ip6.arpa/IN: loaded serial 1645950650
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
101.168.192.in-addr.arpa/IN: sending notifies (serial 1645950657)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.8.10.in-addr.arpa/IN: sending notifies (serial 1645950654)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN: sending notifies (serial 1645950650)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
2.6.5.c.c.9.2.c.4.0.6.5.c.8.d.f.ip6.arpa/IN: loaded serial 1645950658
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa/IN: sending notifies (serial 1645953275)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.f.d.8.4.1.b.e.a.1.3.d.f.ip6.arpa/IN: sending notifies (serial 
1645950650)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa/IN: sending notifies (serial 
1645950660)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone example.com/IN: 
loaded serial 1645950648
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone example.com/IN: 
sending notifies (serial 1645950648)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.7.1.0.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: sending notifies (serial 
1645950656)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
rbl.example.com/IN: loaded serial 1645950657
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN: sending notifies (serial 
1645950655)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.6.d.1.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: sending notifies (serial 
1645950658)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
0.0.9.2.3.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: sending notifies (serial 
1645950658)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone joip.com/IN: 
loaded serial 1645950656
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
2.6.5.c.c.9.2.c.4.0.6.5.c.8.d.f.ip6.arpa/IN: sending notifies (serial 
1645950658)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone 
rbl.example.com/IN: sending notifies (serial 1645950657)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: zone joip.com/IN: 
sending notifies (serial 1645950656)
Feb 27 04:14:36 server.example.com named-pkcs11[1593328]: checkhints: unable to 
get root NS rrset from cache: not found
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
22.75.10.in-addr.arpa/IN: sending notifies (serial 1645950653)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
101.168.192.in-addr.arpa/IN: sending notifies (serial 1645950657)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
0.8.10.in-addr.arpa/IN: sending notifies (serial 1645950654)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
a.b.c.d.e.1.2.3.4.5.0.1.0.0.2.ip6.arpa/IN: sending notifies (serial 1645950650)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa/IN: sending notifies (serial 1645953275)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.f.d.8.4.1.b.e.a.1.3.d.f.ip6.arpa/IN: sending notifies (serial 
1645950650)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
0.0.0.0.3.2.1.a.a.3.2.1.0.1.0.0.2.ip6.arpa/IN: sending notifies (serial 
1645950660)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone example.com/IN: 
sending notifies (serial 1645950648)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
0.0.7.1.0.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: sending notifies (serial 
1645950656)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
0.0.6.d.1.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: sending notifies (serial 
1645950658)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
0.0.9.2.3.3.2.1.6.8.7.3.1.0.0.2.ip6.arpa/IN: sending notifies (serial 
1645950658)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
2.3.4.5.6.7.8.9.d.c.b.a.7.0.6.2.ip6.arpa/IN: sending notifies (serial 
1645950655)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
2.6.5.c.c.9.2.c.4.0.6.5.c.8.d.f.ip6.arpa/IN: sending notifies (serial 
1645950658)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone 
rbl.example.com/IN: sending notifies (serial 1645950657)
Feb 27 04:14:41 server.example.com named-pkcs11[1593328]: zone joip.com/IN: 
sending notifies (serial 1645950656)
Feb 27 04:15:59 server.example.com named-pkcs11[1593328]: client 
@0x7f9a442177e0 10.75.22.247#48983/key linux_home_nsupdate: updating zone 
'example.com/IN': update unsuccessful: brians-honor-8.example.com: 'name not in 
use' prerequisite not satisfied (YXDOMAIN)
Feb 27 04:15:59 server.example.com named-pkcs11[1593328]: client 
@0x7f9a4aa6a3b0 10.75.22.247#48551/key linux_home_nsupdate: updating zone 
'example.com/IN': deleting rrset at 'brians-honor-8.example.com' A
Feb 27 04:15:59 server.example.com named-pkcs11[1593328]: client 
@0x7f9a4aa6a3b0 10.75.22.247#48551/key linux_home_nsupdate: updating zone 
'example.com/IN': adding an RR at 'brians-honor-8.example.com' A 10.75.22.32
Feb 27 04:16:00 server.example.com named-pkcs11[1593328]: client 
@0x7f9a5c0d64c0 10.75.22.247#59717/key linux_home_nsupdate: updating zone 
'22.75.10.in-addr.arpa/IN': deleting rrset at '32.22.75.10.in-addr.arpa' PTR
Feb 27 04:16:00 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=example.com.,cn=dns,dc=example,dc=com 
fa486b2d-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 04:16:00 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2882
Feb 27 04:16:01 server.example.com named-pkcs11[1593328]: client 
@0x7f9a5c0d64c0 10.75.22.247#59717/key linux_home_nsupdate: updating zone 
'22.75.10.in-addr.arpa/IN': adding an RR at '32.22.75.10.in-addr.arpa' PTR 
brians-honor-8.example.com.
Feb 27 04:16:01 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=example.com.,cn=dns,dc=example,dc=com 
fa486b2d-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 04:16:01 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2885
Feb 27 04:16:01 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=22.75.10.in-addr.arpa.,cn=dns,dc=example,dc=com 
fa486b37-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 04:16:01 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2886
Feb 27 04:16:01 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    Detected modify of entry: 
idnsname=22.75.10.in-addr.arpa.,cn=dns,dc=example,dc=com 
fa486b37-3df5-11e5-b0d0-8e21c4e9261b
Feb 27 04:16:01 server.example.com ipa-dnskeysyncd[4725]: 
ipaserver.dnssec.syncrepl: DEBUG    New cookie is: 
server.example.com:389#krbprincipalname=ipa-dnskeysyncd/[email protected],cn=services,cn=accounts,dc=example,dc=com:cn=dns,dc=example,dc=com:(|(objectClass=idnsZone)(objectClass=idnsSecKey)(objectClass=ipk11PublicKey))#2887
Feb 27 04:16:01 server.example.com named-pkcs11[1593328]: zone example.com/IN: 
sending notifies (serial 1645953361)
Feb 27 04:16:01 server.example.com named-pkcs11[1593328]: zone 
22.75.10.in-addr.arpa/IN: sending notifies (serial 1645953362)
Feb 27 04:16:01 server.example.com named-pkcs11[1593328]: checkhints: unable to 
get root NS rrset from cache: not found
Feb 27 04:16:06 server.example.com named-pkcs11[1593328]: zone 
22.75.10.in-addr.arpa/IN: sending notifies (serial 1645953362)

This time it was closer to 45 minutes that my nameserver was answering
queries for local zones with errors instead of results.

Does anyone have any idea why this named is taking so long to load and
serve local zones?  Unsurprisingly, it's really quite disruptive to the
local network to have local zones out of service for 45 minutes.

Cheers,
b.

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
FreeIPA-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/[email protected]
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to