I have tested the dynamic DNS service and noticed
that the registration failed after reboot.
It seems as if the named service was started to late.
Other services like ntpd or fetchmail are also effected, but work
when named finally is running.
messages log file excerpt:
Feb 13 12:50:37 e-smith pppd[484]: local IP address 213.23.54.97
Feb 13 12:50:37 e-smith pppd[484]: remote IP address 145.253.1.227
[...]
Feb 13 12:50:42 e-smith pppoe: Connected!
[...]
Feb 13 12:50:47 e-smith ntpdate[718]: can't find host rustime01.rus.uni-stuttgart.de
Feb 13 12:50:47 e-smith ntpdate[718]: no servers can be used, exiting
[...]
Feb 13 12:50:47 e-smith e-smith[671]: fetchmail: couldn't find canonical DNS name of
pop.puretec.de
[...]
Feb 13 12:50:48 e-smith dyndns.org: Unknown response . Status was 0
[...]
Feb 13 11:51:02 e-smith named[1272]: Ready to answer queries.
Named starts, when I boot into runlevel 5 from the lilo prompt.
Switching then into RL 7 dynamic DNS registration succeeds.
Has anybody else similar problems??
Michael
