Re: 0-TTL when querying "invalid" soa

Perfect.., many thanks for your hints. Tom On 29.01.19 16:33, Tony Finch wrote: Tom wrote: We're running BIND-9.12.3-P1 on our authoritative servers and we have the same behavior with 0-ttl with a invalid soa-query. Is this bind-specific? Why does an invalid soa-record responds with 0-ttl i

Re: 0-TTL when querying "invalid" soa

On Tue, Jan 29, 2019 at 04:23:56PM +0100, Tom wrote: > We're running BIND-9.12.3-P1 on our authoritative servers and we have the > same behavior with 0-ttl with a invalid soa-query. Is this bind-specific? > Why does an invalid soa-record responds with 0-ttl in the authority-section? It appears to

Re: 0-TTL when querying "invalid" soa

Tom wrote: > > We're running BIND-9.12.3-P1 on our authoritative servers and we have the same > behavior with 0-ttl with a invalid soa-query. Is this bind-specific? Why does > an invalid soa-record responds with 0-ttl in the authority-section? Funnily enough, this little obscurity came up elsewhe

0-TTL when querying "invalid" soa

Hi list The following "invalid" soa-query responds with NXDOMAIN and with a ttl of 0 for the SOA-Record in the authoritative section: $ dig +norec +noquestion @ns1.yahoo.com. soa asfasdfdas.yahoo.com ; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> +norec +noquestion @ns1.yahoo.com. soa asfasdfdas.ya