= Сообщение: 3754 из 7440 ============================================= IPV6 = От : Markus Reschke 2:240/1661 20 Nov 16 14:22:50 Кому : Richard Menedetter 20 Nov 16 14:22:50 Тема : Outage FGHI : area://IPV6?msgid=2:240/1661+582b0a5e На : area://IPV6?msgid=2:310/31+58319d58 = Кодировка сообщения определена как: LATIN-1 ================================ Ответ: area://IPV6?msgid=2:310/31+5831b047 ============================================================================== Hi Richard!
Nov 20 13:50 2016, Richard Menedetter wrote to Markus Reschke:
RM> short Update. RM> My NIC was quit nice, and they enabled the NSes (which were by then RM> not authorative). RM> I pressed a button on the he.net page, and all is fine now.
Lucky day. Most NICs test for authoritative nameservers as a requirement for updates. And this can't be circumvented because it's automated that way. And some NICs have obsolete requirements regarding the IP addresses of the nameservers. Once I tried to explain some basics in network engineering and high availability to DeNIC, and that their address requirements for nameservers also violate RIPE's assignment policies. They didn't get it and their reasoning was totally <facepalm>.
Each .de TLD has to have two authoritative nameservers at least. And those nameservers are required to have IPv4 addresses in different /24s. The reason for that is to make sure, that one nameserver is reachable in case of a partial network outage. Small providers simply put both namservers in the same LAN segment, just with addresses in two /24s. DeNIC's requirement was met, but the purpose defeated. And I was not allowed to use two addresses in the same /24 in a high availability data center, each nameserver having two uplinks and running OSPF. We even ran anycast back then across all data centers in the EU for some services. Too advanced for some people ;)
