-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes are ignored when DnsProvider() is not defined #2973
Comments
interesting, how to add glue records? |
Well, let's consider all the possibilities.
That gives us 6 combinations: R:something D:none R:none D:none R:none D:something R:something D:something R:something D:nil R:none D:nil The only combinations that don't make sense are the last two. Both should get warnings. To turn off the warnings, add DnsProvider("NONE"). We can be "smart" by only displaying the warning if there are zone records. To resolve this bug, we should print the warning if |
@tlimoncelli thanks for this clear explanation. 👏🏻 Certainly interesting! Because I have never thought about the situation |
Yeah, the Our legal department periodically asks for a list of all the domains we own. I generally give them the output of I know what you're thinking: Tom, there are domains you don't maintain with DNSControl? How dare you??? Yeah, crazy huh? Well, it happens. For example, I can't maintain Anyway... A few months ago I realized I could define this macro: var REG_THIRDPARTY = NewRegistrar("none");
function INVENTORY_ONLY(name) {
D(name, REG_THIRDPARTY, NO_NS);
} Now we can list those domains are listed in
Now when I run |
Is your feature request related to a problem? Please describe.
A zone defined like the following (without a
DnsProvider()
defined) silently ignores that the TXT record should be created. The required changes are not shown in preview either.When adding
DnsProvider()
the records are correctly added.Describe the solution you'd like
A warning is shown if
DnsProvider()
is not provided so required changes are not suppressed.The text was updated successfully, but these errors were encountered: