Exaweb
Verified User
Hi,
Yesterday, i was doing a upgrade from CentOS 5.3 to CentOS 5.4, which was resulting i following situation.
After doing the upgrade, named failed to start. Starting from command line gave me following error:
As you see, bad configuration file. Normal domain names were loading normally, but IDN names with characters as æ, ø and å were not. They were escaped!
Solution was to delete the domain from the DNS manager in DirectAdmin, and adding it again.
I suggest that DirectAdmin converts those IDN names to the xn- variant, when adding it as a new domain. This will hopefully prevent any issues later..
Yesterday, i was doing a upgrade from CentOS 5.3 to CentOS 5.4, which was resulting i following situation.
After doing the upgrade, named failed to start. Starting from command line gave me following error:
Code:
Error in named configuration:
dns_rdata_fromtext: /var/named/intetdomæne.dk.db:10: near 'hostmaster.intetdomæne.dk.': bad name (check-names)
/var/named/intetdomæne.dk.db:20: ftp.intetdom\230ne.dk: bad owner name (check-names)
/var/named/intetdomæne.dk.db:21: intetdom\230ne.dk: bad owner name (check-names)
/var/named/intetdomæne.dk.db:22: localhost.intetdom\230ne.dk: bad owner name (check-names)
/var/named/intetdomæne.dk.db:23: mail.intetdom\230ne.dk: bad owner name (check-names)
/var/named/intetdomæne.dk.db:24: pop.intetdom\230ne.dk: bad owner name (check-names)
/var/named/intetdomæne.dk.db:25: smtp.intetdom\230ne.dk: bad owner name (check-names)
/var/named/intetdomæne.dk.db:26: www.intetdom\230ne.dk: bad owner name (check-names)
/var/named/intetdomæne.dk.db:28: intetdom\230ne.dk: bad owner name (check-names)
dns_rdata_fromtext: /var/named/intetdomæne.dk.db:28: near 'mail': bad name (check-names)
zone intetdom\230ne.dk/IN: loading master file /var/named/intetdomæne.dk.db: bad name (check-names)
_default/intetdomæne.dk/IN: bad name (check-names)
As you see, bad configuration file. Normal domain names were loading normally, but IDN names with characters as æ, ø and å were not. They were escaped!
Solution was to delete the domain from the DNS manager in DirectAdmin, and adding it again.
I suggest that DirectAdmin converts those IDN names to the xn- variant, when adding it as a new domain. This will hopefully prevent any issues later..