How to Configure Secondary DNS

Webmin
1

Ok this is driving me crazy and no logs are helping.

Main server is Rocky Linux 10.1

SYSTEM INFORMATION
OS type and version Rocky Linux 10.1
Webmin version 2.621
Usermin version 2.521
Virtualmin version 8.0.1 Professional
Theme version 26.22
Apache version 2.4.63
Package updates All installed packages are up to date

Slave DNS Server:

SYSTEM INFORMATION
OS type and version Debian Linux 12
Webmin version 2.621
Theme version 26.22
Package updates All installed packages are up to date

Following the docs: secondary DNS

I add secondary server to main servers index and can connect
when I try to add secondary server in Bind (on main server) all I get is this error:

HTTP/1.0 500 Perl execution failed Server: MiniServ/2.621 Date: Fri, 6 Feb 2026 19:40:41 GMT Content-type: text/html; Charset=utf-8 Connection: close

Error — Perl execution failed
Can't use string ("Failed to connect to fastrpc.cgi"...) as a HASH ref while "strict refs" in use at /usr/libexec/webmin/bind8/slave_add.cgi line 101

Yes searched the forum but nothing has worked that I have found

2

I had this and I think it was a firewall problem. I have a small, inexpensive AWS instance for it. The AWS firewall needed a wider port range. I think 10000 to 10100 is the recommended range now.

3

@ID10T
thanks for the reply
yes ports are open

was working before I upgraded to Rocky Linux 10.1 and VM 8 on main server :frowning:

4

Hmm… I think there was another thread about default hashes configured in Rocky 10. I guess I just saw the first part and it triggered what I remembered.

5

@ID10T
Docs say to check yes for fast rpc calls but that option is not there for now in Rocky Linux 10.1
It was I remember for rocky linux 9.7

Lol every few years it is a struggle with new OS’s changing things

6

@Jamie, can you take a look?

1 Like
7

We have removed it! FastRPC should be the default option now. The lesser options the better.

1 Like
8

Thanks, I see the cause of this confusing error, and will fix it in the next release.

1 Like
9

Just increase the port range (10000+) on your firewall and you will be golden. I added additional 500 ports and it worked immediately… not to mention I spent few hours troubleshooting the error :frowning: