Hello, This a new idea/draft to avoid loss mails during an NS change
Sorry for the ugly write :-X RFC BCP draft purposal *Avoid loss mail during a name server (NS) provider move.* When we want to choose a new NS server/service for our domain name, we can have a tiny delay of several seconds just after typing the new NS on your main DNS hoster interface and the real service activation at the new NS manager hoster. Enough to have possible mail losses. It is often the case when your new commercial NS provider manages tons of NS (and need to know, thanks to your NS changes, than you are the real owner). I purpose than a TXT filed on the former NS root could be created with any of the future desired NS changes "ns1_future:ns1.my_future_ns_provider.com" "ns2_future:ns2.my_future_ns_provider.com" Example: I actually use "ns1.former_ns_manager.com" and "ns2.former_ns_manager.com" on my DNS hoster "ns1.new_ns_manager.com" and "ns2.new_ns_manager.com" changes made can be only detected by the new NS manager alsmost several seconds after the real change and can occurs loss messages during this time :-( By using these 2 TXT fields created on my former NS manager .... seb@seb:~$ dig TXT vivilproject.com ; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> TXT vivilproject.com (...) ;; ANSWER SECTION: vivilproject.com. 3600 IN TXT "ns2_future:ns2.future_ns_provider.com" vivilproject.com. 3600 IN TXT "ns1_future:ns1.future_ns_provider.com" ...... "future_ns_provider.com" can easily read the TXT field and he will knows for sure i want to shortly use his service and, with this information, he can temporary activate my account and authorize mail routing during a definited time of X hours or Y days. So i have the time to calmly change these two NS on my DNS hoster. Two steps but 0 loss.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
