google-nomulus/docs
mcilwain ff3aeff0ed Remove per-domain nameserver restrictions in reserved lists
This also removes the related setting on the Registry entity. We never used
either of these, and keeping them around in our codebase just adds complexity
for no purpose. We already achieve the goals of this feature by restricting
nameservers on entire TLDs and by registry-locking important domain names.

This is also two fewer things we'll have to worry about carrying over to the new
schema in Registry 3.0.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=243816241
2019-04-16 14:09:27 -04:00
..
operational-procedures Explain SERVER_HOLD part of NAME_COLLISION reservations 2019-02-06 18:01:37 -05:00
admin-tool.md Remove references to Eclipse 2018-03-19 18:45:41 -04:00
architecture.md Delete remnants of registrar-level credits 2018-06-27 15:28:52 -04:00
authentication-framework.md Add documentation for AUTH_PUBLIC_OR_INTERNAL 2018-06-18 18:03:29 -04:00
code-structure.md Update generate_workspace link 2017-11-21 18:28:43 -05:00
coding-faq.md Refer to Datastore everywhere correctly by its capitalized form 2017-02-17 12:12:12 -05:00
configuration.md Update documentation on nomulus tool authentication 2019-01-17 19:22:25 -05:00
developing.md Add link to final ReferenceUnion migration commit in Developing doc 2016-11-15 15:15:55 -05:00
first-steps-tutorial.md Update create_domain command documentation 2017-08-01 16:53:32 -04:00
flows.md Remove per-domain nameserver restrictions in reserved lists 2019-04-16 14:09:27 -04:00
install.md Update to bazel 0.23.1 2019-03-08 18:41:16 -05:00
operational-procedures.md Clarify diff display of MutatingCommand 2017-10-04 16:16:45 -04:00
proxy-setup.md Store encrypted file in Base64 encoding 2018-06-18 17:53:11 -04:00
rdap.md Fix cut-and-paste error in RDAP documentation 2018-03-19 18:31:15 -04:00
registrar-faq.md Add Registrar FAQ document 2016-10-24 10:55:37 -04:00