Re: id.server on 9.18.24

2024-02-14 Thread Marco Davids (SIDN) via bind-users
Solved by adding 'server-id' to named.conf.options. Thank you Petr Špaček for the suggestion. Op 14/02/2024 om 10:23 schreef Marco Davids (SIDN): I have upgraded two servers to 9.18.24 and the funny thing is that on one server id.servers works well: ;; ANSWER SECTION: id.server.    0   

Re: id.server on 9.18.24

2024-02-14 Thread Ondřej Surý
Hey, could you run the other server manually with same configuration but on a different port and enable -d 99 on a command line? That could give some hints. -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not feel obligated to reply outside your

id.server on 9.18.24

2024-02-14 Thread Marco Davids (SIDN) via bind-users
I have upgraded two servers to 9.18.24 and the funny thing is that on one server id.servers works well: ;; ANSWER SECTION: id.server. 0 CH TXT "one" And on the other it does not: ;; AUTHORITY SECTION: id.server. 86400 CH SOA id.server. hostmaster.id.server. 0 28800