Discovered that when you delete a Route53 zone there is NO way to put it back with the same nameservers, even though those nameservers were gonna be cached by a major national ISP for a couple days. (Did my best social engineering ever to get a DNS admin at that ISP paged, tho)https://twitter.com/ElleArmageddon/status/1255870742727585792 …
-
-
-
-
Replying to @substitute @_r_o_n_e_
(Reusable delegation sets are an insurance policy against this, fwiw. But this was right after the infamous Dyn outage, and we had moved to R53 in a hurry.)
1 reply 0 retweets 1 like -
Also I couldn’t remember the term “reusable delegation set” and in googling I found this great bit of instruction from AWS https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/white-label-name-servers.html …pic.twitter.com/9ZyZt0rR7t
1 reply 0 retweets 1 like -
Replying to @mendel @_r_o_n_e_
when you reach the ground, locate the duty sergeant and report the parachute failure
1 reply 0 retweets 2 likes
found another gem. now that you’ve done all those steps, now just give Google and OpenDNS a ring and have them set you uppic.twitter.com/tzYqqZ737f
-
-
Replying to @mendel @_r_o_n_e_
this one weird trick for saving your dns, click to find out
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.