← Back to context Comment by embedding-shape 4 hours ago That's not true though, sometimes it's inexplicitly DNS too. 5 comments embedding-shape Reply schmuckonwheels 4 hours ago My money is on expired certificate.If so, successful test. Xylakant 3 hours ago The great thing is that with all of the encrypted/signed DNS thingys, you now have not one, but multiple options to combine “invalid certificate” and DNS in one outage. You no longer need to choose! snorbleck 4 hours ago it's always DNS zekyl314 4 hours ago or BGP. montjoy 2 hours ago No no it’s gotta be “the database”
schmuckonwheels 4 hours ago My money is on expired certificate.If so, successful test. Xylakant 3 hours ago The great thing is that with all of the encrypted/signed DNS thingys, you now have not one, but multiple options to combine “invalid certificate” and DNS in one outage. You no longer need to choose!
Xylakant 3 hours ago The great thing is that with all of the encrypted/signed DNS thingys, you now have not one, but multiple options to combine “invalid certificate” and DNS in one outage. You no longer need to choose!
snorbleck 4 hours ago it's always DNS zekyl314 4 hours ago or BGP. montjoy 2 hours ago No no it’s gotta be “the database”
My money is on expired certificate.
If so, successful test.
The great thing is that with all of the encrypted/signed DNS thingys, you now have not one, but multiple options to combine “invalid certificate” and DNS in one outage. You no longer need to choose!
it's always DNS
or BGP.
No no it’s gotta be “the database”