prefetch will ask for the CNAME but that is in the background and shouldn’t impact normal resolution. The log however will be noisy.On 14 May 2022, at 00:02, Ondřej Surý wrote:I think you misdiagnosed the issue.Nothing asks directly for the CNAME under normal circumstances, andAnd IN A query retu
Ok understood !
Do you have any opinion on the multi CNAME behavior at the authoritative
server ?
In python (in the analyzed case), the CNAME resolution will give you the
second entry generating a dnssec validation failure.
Yes it is a bit convoluted :
- one program said "hey, this entry is
I think you misdiagnosed the issue.
Nothing asks directly for the CNAME under normal circumstances, and
And IN A query returns:
$ dig IN A lb.qual.flash-global.net @ns-160-c.gandi.net.
; <<>> DiG 9.19.0-1+0~20220421.76+debian10~1.gbpa71ef8-Debian <<>> IN A
lb.qual.flash-global.net @ns-160-c.ga
Hello,
I've had a hard time identifying the source of intermittent name
resolution failure for a customer.
The source of the problem is a DNS spec violation with a RRSET with
multiple CNAME:
dig @ns-29-b.gandi.net CNAME lb.qual.flash-global.net
; <<>> DiG 9.18.2-1+ubuntu20.04.1+isc+3-Ubuntu <<>
4 matches
Mail list logo
