Hi Fulvio, i noticed that when i make a minor change to bind configuration using the web frontend, forwarders start working due to bind service is rebooted. May be there is a way to reboot bind remotelly using ssh when the forwarder is rebooted.
Which is the command-line for rebooting bind?
if a make a call remotely using ssh , will console frontend (that is shown when login) be a problem? and how can i disable it?
Hi, thanks for the quick response. Each host in the intranet has as default gateway and nameserver a zeroshell router which(192.168.0.2). If t any resolution request matches with a registered forwarder, it forwards the dns requirement to my vpngateway (192.168.0.3). There, dnsmask forward the request thru vpn where it is finally resolved. The dnsmask uses vpn configuration that is automatically set by vpnc (cisco client.) For example an scenario can be: A hosts (192.168.0.111) request a dns resolution ZS router check if it matches with a forwarder The request is forwarded to the vpn gateway(192.168.0.3) It is finally resolved