jojolafrite
Verified User
- Joined
- Sep 19, 2014
- Messages
- 53
Hi,
Issue with Directadmin with Debian 7 fresh install Everything is fine for me with Centos 6.6
After changing records in any Dns zone files in Directadmin panel.
Let's imagine i add a TXT record to mydomain.com then i type...
dig mydomain.com TXT @127.0.0.1 +norecurse from ssh terminal
i see no changes
i have to do a
service named restart or
service named reload or
rndc reload
to have the visible update with dig
I wonder whether there is no job that is broken to do a "rndc reload" after any changes to DNS zones in Directadmin panel.
in order to replicate the error:
1. Go to DNS management at user level for one domain
2. Add a TXT record
3. connect to Ssh
4. install dig if it is not yet installed by doing apt-get install dnsutils
5. dig yourdomain.com TXT @127.0.0.1 to see if the change is available
Workaround:
Creation of a cron job to reload the DNS zone files every 10 minutes:
*/10 * * * * /usr/sbin/rndc reload
UPDATE:
This server ran on Debian 8 & the directadmin license was for Debian 7. Consequently, Directadmin installed the Debian 7 version on Debian 8. It was the reason why it was doing it. Fix: fast migration to a Debian 7 VM.
Issue with Directadmin with Debian 7 fresh install Everything is fine for me with Centos 6.6
After changing records in any Dns zone files in Directadmin panel.
Let's imagine i add a TXT record to mydomain.com then i type...
dig mydomain.com TXT @127.0.0.1 +norecurse from ssh terminal
i see no changes
i have to do a
service named restart or
service named reload or
rndc reload
to have the visible update with dig
I wonder whether there is no job that is broken to do a "rndc reload" after any changes to DNS zones in Directadmin panel.
in order to replicate the error:
1. Go to DNS management at user level for one domain
2. Add a TXT record
3. connect to Ssh
4. install dig if it is not yet installed by doing apt-get install dnsutils
5. dig yourdomain.com TXT @127.0.0.1 to see if the change is available
Workaround:
Creation of a cron job to reload the DNS zone files every 10 minutes:
*/10 * * * * /usr/sbin/rndc reload
UPDATE:
This server ran on Debian 8 & the directadmin license was for Debian 7. Consequently, Directadmin installed the Debian 7 version on Debian 8. It was the reason why it was doing it. Fix: fast migration to a Debian 7 VM.
Last edited: