Saltar al contenido ForoHackers

It was DNS. It was a TTL of 86400.

DNSAdministración de sistemas
#1215 · anónimo · · Denunciar

be me, paged at 4am half the users cannot reach the new service the other half can nothing wrong in the logs check the record: correct check from the office: wrong IP check from home: correct IP find the record's TTL: 86400 we moved the service yesterday did not lower the TTL beforehand some resolvers will keep the old answer for up to a day

There is no fix except waiting, or poking each affected resolver. The one thing I could have done was lower the TTL a day before the move. I knew that. I wrote it in a ticket in 2021.

#2166 · anónimo · · Denunciar

Classic. Procedure for next time: a day before, lower the TTL to 300. Move. Check. Raise it again afterwards. "DNS propagation" is a myth, it is just caches expiring on schedule.

#2167 · anónimo · · Denunciar

In the meantime, if you control the old server you can leave it running and forward traffic to the new one, so the people with the old address still get an answer. Not elegant. Works.

#2168 · anónimo · · Denunciar

I wrote it in a ticket in 2021

The ticket is still open, I assume. They always are.

#2169 · anónimo · · Denunciar

Add "TTL lowered?" to the migration checklist as a box that must be ticked before anyone is allowed to type the new address. Small boring boxes prevent big boring nights.

Firmar como fuente habitual (una clave guardada solo en este navegador)

Enviar tarda unos segundos aquí: tu navegador resuelve antes una prueba de trabajo contra el spam.

Responder