Results 1 to 4 of 4

Thread: Named and unsupported sign in config

  1. #1
    Join Date
    Jun 2018
    Posts
    38

    Named and unsupported sign in config

    Hi,
    we just had some downtime because of named, which didn't wanted to restart, I found a problem in named config, which was created by directadmin,
    there was an unsupported sign in domain name, which caused that named couldn't restart. Is it possible that it is directadmin bug?

  2. #2
    Join Date
    Apr 2009
    Posts
    2,340
    You should add "allow_domain_special_characters=0" to directadmin.conf and restart DirectAdmin. More infomation here: https://www.directadmin.com/features.php?id=2082

    Edit: Or you could instead enable this feature to automatically convert to punycode: https://www.directadmin.com/features.php?id=1482
    Last edited by ditto; 07-27-2019 at 11:38 PM.

  3. #3
    Join Date
    Jun 2018
    Posts
    38
    Thanks, I think that it should be default.

  4. #4
    Join Date
    Apr 2009
    Posts
    2,340
    The problem is that Enhanced skin is using iso-8859-1, but convert to punycode at https://www.directadmin.com/features.php?id=1482 require UTF-8 to work. And also Evolution has already built in support for puny code conversion. So puny code conversion can't be default.

    Then disabling special characters at https://www.directadmin.com/features.php?id=2082 also can not be default, because that would break puny code conversion if you use Evolution skin.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •