TXT records lose spaces when added via CLI or API

Hello,

We are having problems adding a TXT record to DNS through Virtualmin.

When we run:

virtualmin modify-dns --domain example.com --add-record "example.com. TXT This is an test"

…the record that gets written is:

example.com.   TXT   "Thisisantest"

All spaces are stripped.

The same issue happens when using the Virtualmin API. We tried encoding the value using both urlencode and rawurlencode, but the result is always the same: TXT values lose their spaces.

Expected result:

example.com.   TXT   "This is an test"

Actual result:

example.com.   TXT   "Thisisantest"

Are we doing something wrong, or is this a bug in the CLI/API TXT record handling?

OS : Debian 12.12
Webmin version 2.402
Virtualmin version 7.30.8

I get the same, I tried this as well and still stripes the spaces.
virtualmin modify-dns --domain example.com --add-record "example.com TXT \"This is and test\""

It work fine in the GUI. (workaround)

Seems like a bug.

That’s what I thought. Now I just need to find an alternative way to script this change, since we can’t update it through the GUI due to the large number of changes required.

Also, how quickly are bugs like this usually picked up and fixed?

usability bugs are usually picked up really quickly. Ilia has just dropped a big virtualmin release so hang tight.

You can always do a proper bug report at GitHub and link it here.

It might not be relevant but Webmin is now on 2.501

so might have already been fixed.

if not you usually get at least an acknowledgment as staff keep an eye open for such things it is then just a matter of patience.

The problem still exists in the latest release and unfortunately has not been resolved yet.

I have verified this on a fully updated system with the following versions installed:

  • Webmin version:** 2.501
  • Usermin version:** 2.400
  • Virtualmin version:** 7.40.0

So it seems the issue is not related to an outdated installation.

OK, 2.501 is only just out (some might not even have noticed yet) as I mentioned we all need to exercise a certain level of patience for these bugs to be prioritised and fixed.

This issue has been resolved, and the fix will be delivered in the next release.

1 Like

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.