Skip to content
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

[ISSUE] fmDNS warning creating and reloading zones: "dn_to_utf8(): INTL_IDNA_VARIANT_2003 is deprecated" #481

4 of 5 tasks
andrewhotlab opened this issue Mar 16, 2020 · 5 comments


Copy link

fM Version : 3.5.7
fmdns Version : 3.4.1

In raising this issue, I confirm the following:

  • I have read and understood the contributors guide.
  • I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
  • I have checked that the issue I'm posting isn't already reported.
  • I have checked that the issue I'm posting isn't already solved and no duplicates exist in closed issues and opened issues
  • I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.

Expected Behavior:
Have the new zone dialog or the reload function displayed/act without errors.

Actual Behavior:
When creating a new zone, the dialog does not appear (thus it has become impossible to create new zones). See attached screenshot.


When reloading a zone, it displays the following error, but the process ends successfully.

Deprecated: idn_to_utf8(): INTL_IDNA_VARIANT_2003 is deprecated in [DocumentRoot]/fm-modules/fmDNS/functions.php on line 777

Steps to reproduce:
Click on Zones > Forward > Add New

I was unable to reproduce the problem on a staging fm instance, thus I guess its someway related to PHP configuration of the production web server. Both of them runs Apache httpd 2.4.41 and PHP 7.2.26 (and PHP intl extension) on FreeBSD 11.3.
I'd be grateful if someone can suggest me what to check.

Copy link

WillyXJ commented Mar 16, 2020

The usage of idn_to_utf8() in fmDNS does not specify a variant so it's relying on the default or server's configuration. I see INTL_IDNA_VARIANT_2003 was deprecated in PHP 7.2, but they did not change the default so you're getting those warnings (see

Until a fix is implemented in fmDNS to explicitly define the variant, you can disable the errors in the Settings which should allow you to manage your zones.

@WillyXJ WillyXJ added the fmDNS label Mar 16, 2020
Copy link

Thank you, but maybe I'm missing the right setting... I already have these lines in both servers' php.ini file:

display_errors = Off
display_startup_errors = Off
track_errors = Off

Copy link

WillyXJ commented Mar 16, 2020

This should be done in the facileManager settings as shown in this screenshot. This may also be the difference between your production and pre-production environments.

Screen Shot 2020-03-16 at 3 21 12 PM

Copy link

WillyXJ commented Oct 24, 2020

This is now fixed in fmDNS 4.0-beta1 and later. Final release will come out later.

Copy link

WillyXJ commented Nov 11, 2020

fmDNS 4.0.0 has been released.

@WillyXJ WillyXJ closed this as completed Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants