Problem with Bind in Plesk

S

S.AliZ

Guest
Hi dear all ,

Last week i had installed plesk control panel on my debian lenny server. All services work fine except bind.
I don't know why but when i create a domain,automatically plesk creates necessary records for dns but nothing happen to named.conf or named.conf.options or named.conf.local .
I think plesk doesn't connect to bind because when i create zones manually everything is correct so what could i do ?
 
Strange. I have checked on fresh Plesk 9.3.0 and found that /etc/named.conf is symlink and it is updated by Plesk with new records about added domains:

# ls -la /etc/named.conf
lrwxrwxrwx 1 root root 34 Jan 14 06:14 /etc/named.conf -> /var/named/run-root/etc/named.conf
 
thanx IgorG for your replay

you are right but there is problem :
The main bind configuration is in /etc/bind/named.conf & plesk insert it's named.conf in /etc .
I was trying to replace them with each others but bind failed to start ,
now what should i do ?
 
Not sure why you have it in /etc/bind/named.conf but by default it should be as symlink in /etc/named.conf
What is OS you have?
 
Do you see in /var/log/messages that zones are loaded correctly when you restart named service?
 
Just restart named service and check output in /var/log/messages log file.
 
nothing happen when i reset bind service or psa services.
no details has been added to the message log .
 
What do you mean 'reset'? You should restart it with

/etc/init.d/named restart

After that check /var/log/messages
 
I know what you mean ( in debian : /etc/init.d/bind9 restart or for plesk /etc/init.d/psa restart ) but the messages file does not change.
maybe you want to know software process log in debian that store in /var/log/syslog . am i right?
 
Yes, unfortunately I haven't any accessible Debian system now for checking. Seems you are correct.
 
not at all , just the default zones that store in /etc/bind/named.conf are loaded.
 
Well. I have checked named on Lenny with Plesk. I see following:

plesk9:~# cat /etc/issue
Debian GNU/Linux 5.0 \n \l

plesk9:~# ls -la /etc/named.conf
lrwxrwxrwx 1 root root 34 Nov 26 07:43 /etc/named.conf -> /var/named/run-root/etc/named.conf

plesk9:~# less /etc/named.conf
.......
zone "test.com" {
type master;
file "test.com";
allow-transfer {
123.123.123.123;
common-allow-transfer;
};
};
zone "testdomain.com" {
type master;
file "testdomain.com";
allow-transfer {
10.55.62.2;
common-allow-transfer;
};
};
..........

In /var/log/syslog after named restarting:

Jan 28 13:53:47 plesk9 named[5790]: zone 62.55.10.in-addr.arpa/IN: loaded serial 1263676849
Jan 28 13:53:47 plesk9 named[5790]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
Jan 28 13:53:47 plesk9 named[5790]: zone test.com/IN: loaded serial 1262030034
Jan 28 13:53:47 plesk9 named[5790]: zone testdomain.com/IN: loaded serial 1263676849
Jan 28 13:53:47 plesk9 named[5790]: running

Not sure how and why you have your named configuration.
 
during last night i was trying to reinstall
plesk on new debian lenny .
after reinstallation i understood that domain had been loaded in syslog.

##################################
Jan 29 11:28:54 localhost named[6881]: received SIGHUP signal to reload zones
Jan 29 11:28:54 localhost named[6881]: loading configuration from '/etc/named.conf'
Jan 29 11:28:54 localhost named[6881]: max open files (1024) is smaller than max sockets (4096)
Jan 29 11:28:54 localhost named[6881]: using default UDP/IPv4 port range: [1024, 65535]
Jan 29 11:28:54 localhost named[6881]: using default UDP/IPv6 port range: [1024, 65535]
Jan 29 11:28:54 localhost named[6881]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 29 11:28:54 localhost named[6881]: command channel listening on 127.0.0.1#953
Jan 29 11:28:54 localhost named[6881]: reloading configuration succeeded
Jan 29 11:28:54 localhost named[6881]: zone 1.10.10.in-addr.arpa/IN: loaded serial 1264751934
Jan 29 11:28:54 localhost named[6881]: zone newtest.com/IN: loaded serial 1264751933
Jan 29 11:28:54 localhost named[6881]: reloading zones succeeded
##################################

for example when i create firsttest.com then i can preview it with
https://localhost:8443/sitepreview/http/firsttest.com/ but when i am
trying to preview firsttest.com/ directly i get failed .
i want send you syslog file & /etc/bind & /var/named that could be help you
to realize what is the problem .
could you please tell me your mail ?
 
Is domain firsttest.com resolvable from your workstation? If I correctly understood you have DNS server configured for private network? Do you have A record for this domain?
 
Back
Top