Unable to use this plugin about alternate

[chrisohaver]

In what order are forward and alternate plugins listed in your plugin.cfg?

[chrisohaver]

Same as in README.md: first forward, then alternate.

The readme shows several Corefile examples.... but the Corefile is different than the /plugin.cfg file that you are required to change in CoreDNS when compiling in external plugins, such as this one. A very common mistake is to add external plugins to the end of the list, but plugin.cfg defines execution order of plugins. The order of plugins the Corefile does not matter. If forward is executed before alternate, alternate never processes anything.

[isavcic]

Same here. Compiled against v1.8.0 CoreDNS. Compilation goes okay, but:

. {
        forward . 104.199.179.254
        alternate REFUSED . 1.1.1.1
}

returns REFUSED, but when configuration is changed to forward to 1.1.1.1 (without alternate), the 1.1.1.1 resolver can of course resolve the record; tried with google.com A.

BTW, @OriolOMM you can see the plugin is "running" because CoreDNS doesn't complain there's the keyword alternate.

[isavcic]

I wonder, why didn't the tests catch this?

[isavcic]

Same as in README.md: first forward, then alternate.

[isavcic]

@chrisohaver Wow, thanks! Sorry, I misread, I thought you meant Corefile... Indeed, when I put alternate on top of plugin.cfg and recompiled, it works!

[OriolOMM]

Changing the order of the plugin in plugin.cfg worked. Thanks