Local machine won't update, remote does.

Started by Nick Cockinos, April 19, 2005, 12:58:08 AM

Previous topic - Next topic

Nick Cockinos

Hi All,
I have a weired one for you all.

A while ago I set up NicTool and it's been running fine, however the local machine, running both server and client, doesn't update itself.

It does update the remote ns2 machine quite successfully.

I've checked permissions on /usr/local/tinydns and they are set to tinydns:tinydns for all directories and files.

Should the local machine show updates in the nameserver status?








LogicX

You're just going to have to troubleshoot the problem?

Have you verified that the tinydns user can ssh to the ns1.machine.com w/o error? (does it have the ssh keys setup correctly? is the host in the know_hosts file? have you changed the IP of ns1.machine.com; and does known_hosts reflect that?)

does the export script show any errors? (/home/tinydns/ns1.domain.com/log/main/current in my setup)

--- May this post be indexed by spiders, and archived for all to see as my internet epitaph.
http://fpux.com" target="_blank">http://fpux.com

Nick Cockinos

Is it necessary to have ssh keys setup even if the ns1 machine is local?

LogicX

yes

essentially there's no difference between one of the servers serving the DNS responses using tinydns -- and the machine that happens to be the one with the database -- there's no 'special treatment' Wink
--- May this post be indexed by spiders, and archived for all to see as my internet epitaph.
http://fpux.com" target="_blank">http://fpux.com