Bind Problems

[kevindevaux]

I installed the perl.5.8.6 and I didnt get any errors and i thank you. but when I try to add a dns to A record to one of my domain.. then try
to look it up its says its not reporting that record but if I disable the dns for the domain switch and then enable again it can look up the domain and the dns just fine can you tell me what I am doing wrong ?

 

[jamesyeeoc]

Plesk is supposed to restart bind/named automatically. It sounds as if it is unable to do that, or maybe your Plesk install is corrupted. You may want to first check your logs immediately after making a change to the DNS to see if there are any errors logged. I don't remember if you are running RH or not, but if so, then 'tail -f /var/log/messages'. Upon restarting, you should see a message similar to 'named startup succeeded' in the log.

 

[kevindevaux]

its freebsd 5.3 this is what i got for a responses. the bind starts and stops when i restart it from with inside plesk.

WebServer# tail -f /var/log/messages
Aug 7 01:25:21 WebServer named[301]: starting BIND 9.3.0 -u bind -c /etc/named.conf -t /usr/local/psa/named/run-root
Aug 7 01:25:21 WebServer named[301]: command channel listening on 127.0.0.1#953
Aug 7 01:27:15 WebServer su: DeVauX to root on /dev/ttyp0
Aug 7 01:29:31 WebServer named[1319]: starting BIND 9.3.0 -u bind -c /etc/named.conf -t /usr/local/psa/named/run-root
Aug 7 01:29:31 WebServer named[1319]: command channel listening on 127.0.0.1#953
Aug 7 02:43:37 WebServer named[4589]: starting BIND 9.3.0 -u bind -c /etc/named.conf -t /usr/local/psa/named/run-root
Aug 7 02:43:37 WebServer named[4589]: command channel listening on 127.0.0.1#953
Aug 7 02:44:02 WebServer su: DeVauX to root on /dev/ttyp0
Aug 7 02:45:03 WebServer named[4924]: starting BIND 9.3.0 -u bind -c /etc/named.conf -t /usr/local/psa/named/run-root
Aug 7 02:45:03 WebServer named[4924]: command channel listening on 127.0.0.1#953

 

[jamesyeeoc]

Looks ok to me. There are 4 pairs of entries. Each time it starts up, it is logging the 'Starting', then the result 'command channel listening'.

So if you manually restarted it (or made changes) 4 times, then this looks perfectly normal.

 

[kevindevaux]

ok this just an A record I just added kevin.frenchroyalhosting.net. A 6.6.6.6
in plesk..
1. Step 1:

[10:59] * Dns resolving kevin.frenchroyalhosting.net
-
[10:59] * Dns unable to resolve kevin.frenchroyalhosting.net

setup 2:

1.DNS Lookup: kevin.frenchroyalhosting.net A record
Generated by www.DNSstuff.com

How I am searching:
Searching for kevin.frenchroyalhosting.net A record at i.root-servers.net [192.36.148.17]: Got referral to E.GTLD-SERVERS.net. [took 7 ms]
Searching for kevin.frenchroyalhosting.net A record at E.GTLD-SERVERS.net. [192.12.94.30]: Got referral to nj2.frenchroyalhosting.us. [took 74 ms]
Searching for kevin.frenchroyalhosting.net A record at nj2.frenchroyalhosting.us. [66.111.217.166]: Reports that no A records exist. [took 44 ms]

Answer:
No A records exist for kevin.frenchroyalhosting.net. [Neg TTL=86400 seconds]

Details:
nj2.frenchroyalhosting.us. (an authoritative nameserver for frenchroyalhosting.net.) says that there are no A records for kevin.frenchroyalhosting.net.
The E-mail address in charge of the frenchroyalhosting.net. zone is: [email protected].



______________________________

ok that before i restart bind from within side Plesk:



This is after I restarted bind with Plesk I cant figure out the problem:

How I am searching:
Searching for kevin.frenchroyalhosting.net A record at j.root-servers.net [192.58.128.30]: Got referral to B.GTLD-SERVERS.net. [took 90 ms]
Searching for kevin.frenchroyalhosting.net A record at B.GTLD-SERVERS.net. [192.33.14.30]: Got referral to nj2.frenchroyalhosting.us. [took 212 ms]
Searching for kevin.frenchroyalhosting.net A record at nj2.frenchroyalhosting.us. [66.111.217.166]: Reports kevin.frenchroyalhosting.net. [took 9 ms]

Answer:


Domain Type Class TTL Answer
kevin.frenchroyalhosting.net. A IN 86400 6.6.6.6
frenchroyalhosting.net. NS IN 86400 ns.frenchroyalhosting.net.
ns.frenchroyalhosting.net. A IN 86400 66.111.217.165

 

[jamesyeeoc]

Right, that's what I suspected in the first place. It appears that Plesk is not automatically restarting your bind/named service upon changing the DNS for the domain.

As a possible workaround, if you are using Plesk 7.5.3, you can go to Server - Event Manager. Create a new Event Handler. Pick 'Domain DNS zone updated', pick a priority, User 'root', fill in the command for your OS to restart bind. Then test again.