• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

DDclient will nicht

J

James28

Hallo zusammen

Habe ein Problem mit dem DDclient. Ich habe in der Config alles eingetragen aber trozdem kann ich auf meine seiten nicht zugreifen von aussen weis jemand ob es einen Testbefehl zum testen vom ddclient gibt.

Ichz verwende den Suse Linux Open schoolserver.

Gruß James28
 
B

b3ll3roph0n

Distribution? Version?
ddclient.conf ?

Läuft ddclient überhaupt?
Als Dämon? Als ipup-Script?

Rechner direkt am Netz? Hinter Router?

Fragen über Fragen ....
 
OP
J

James28

ich habe den Suse Linux Open School Server der aud Suse Linux Enterprise 9 basiert.
Der Serer hängt direckt am Router (d-Link 624+ Wlan nichtaktiv).
Hier meine ddclient.conf:

######################################################################
##
## Define default global variables with lines like:
## var=value [, var=value]*
## These values will be used for each following host unless overridden
## with a local variable definition.
##
## Define local variables for one or more hosts with:
## var=value [, var=value]* host.and.domain[,host2.and.domain...]
##
## Lines can be continued on the following line by ending the line
## with a \
##
######################################################################
daemon=300 # check every 300 seconds
syslog=yes # log update msgs to syslog
mail=root # mail all msgs to root
mail-failure=root # mail failed update msgs to root
pid=/var/run/ddclient.pid # record PID in file.
#
#use=watchguard-soho, fw=192.168.111.1:80 # via Watchguard's SOHO FW
#use=netopia-r910, fw=192.168.111.1:80 # via Netopia R910 FW
#use=smc-barricade, fw=192.168.123.254:80 # via SMC's Barricade FW
#use=netgear-rt3xx, fw=192.168.0.1:80 # via Netgear's internet FW
#use=linksys, fw=192.168.1.1:80 # via Linksys's internet FW
#use=maxgate-ugate3x00, fw=192.168.0.1:80 # via MaxGate's UGATE-3x00 FW
#use=elsa-lancom-dsl10, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router
#use=elsa-lancom-dsl10-ch01, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router
#use=elsa-lancom-dsl10-ch02, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router
#use=alcatel-stp, fw=10.0.0.138:80 # via Alcatel Speed Touch Pro
#use=xsense-aero, fw=192.168.1.1:80 # via Xsense Aero Router
#use=allnet-1298, fw=192.168.1.1:80 # via AllNet 1298 DSL Router
#use=3com-oc-remote812, fw=192.168.0.254:80 # via 3com OfficeConnect Remote 812
#use=e-tech, fw=192.168.1.1:80 # via E-tech Router
#use=cayman-3220h, fw=192.168.0.1:1080 # via Cayman 3220-H DSL Router
use=D-link624+, fw=192.168.1.1:80 # via D-link 624+ DSL Router

#
#
fw-login=admin, fw-password=XXXXXX # FW login and password
#
## To obtain an IP address from FW status page (using fw-login, fw-password)
#use=fw, fw=192.168.1.254/status.htm, fw-skip='IP Address' # found after IP Address
#
## To obtain an IP address from Web status page (using the proxy if defined)
#use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP Address
#
use=ip, ip=127.0.0.1 # via static IP's
use=if, if=eth0 # via interfaces
use=web # via web
#
#protocol=dyndns2 # default protocol
#proxy=fasthttp.sympatico.ca:80 # default proxy
#server=members.dyndns.org # default server
#server=members.dyndns.org:8245 # default server (bypassing proxies)

#login=your-login # default login
#password=test # default password
#mx=mx.for.your.host # default MX
#backupmx=yes|no # host is primary MX?
wildcard=yes|no # add wildcard CNAME?

login=************ # default login
password=****** # default password
#mx=mx.for.your.host # default MX
#backupmx=yes|no # host is primary MX?
wildcard=yes

##
## dyndns.org dynamic addresses
##
## (supports variables: wildcard,mx,backupmx)
##
# server=members.dyndns.org, \
# protocol=dyndns2 \
# your-dynamic-host.dyndns.org

server=members.dyndns.org, \
protocol=dyndns2 \
meineseite.dyndns.org


server=members.dyndns.org, \
protocol=dyndns2 \
millerlite.dyndns.org
##
## dyndns.org static addresses
##
## (supports variables: wildcard,mx,backupmx)
##
# static=yes, \
# server=members.dyndns.org, \
# protocol=dyndns2 \
# your-static-host.dyndns.org

##
##
## dyndns.org custom addresses
##
## (supports variables: wildcard,mx,backupmx)
##
# custom=yes, \
# server=members.dyndns.org, \
# protocol=dyndns2 \
# your-domain.top-level,your-other-domain.top-level

##
## ZoneEdit (zoneedit.com)
##
# server=www.zoneedit.com, \
# protocol=zoneedit1, \
# login=your-zoneedit-login, \
# password=your-zoneedit-password \
# your.any.domain,your-2nd.any.dom

##
## EasyDNS (easydns.com)
##
# server=members.easydns.com, \
# protocol=easydns, \
# login=your-easydns-login, \
# password=your-easydns-password \
# your.any.domain,your-2nd.any.domain

##
## Hammernode (hn.org) dynamic addresses
##
# server=dup.hn.org, \
# protocol=hammernode1, \
# login=your-hn-login, \
# password=your-hn-password \
# your-hn-host.hn.org,your-2nd-hn-host.hn.org

##
## dslreports.com dynamic-host monitoring
##
# server=members.dslreports.com \
# protocol=dslreports1, \
# login=dslreports-login, \
# password=dslreports-password \
# dslreports-unique-id

##
## OrgDNS.org account-configuration
##
# use=web, web=members.orgdns.org/nic/ip
# server=www.orgdns.org \
# protocol=dyndns2 \
# login=yourLoginName \
# password=yourPassword \
# yourSubdomain.orgdns.org

##
## dnspark.com
## (supports variables: mx, mxpri)
##
# use=web, web=ipdetect.dnspark.com, web-skip='Current Address:'
# protocol=dnspark, \
# server=www.dnspark.com, \
# your-host.dnspark.com

##
## NameCheap (namecheap.com)
##
# protocol=namecheap, \
# server=dynamicdns.park-your-domain.com, \
# login=my-namecheap.com-login, \
# password=my-namecheap.com-password \
# myhost.namecheap.com

Wie kann ich denn das sehen ob der läuft gibs da nen befehl und wie mache ich den lauffähig.

Gruß James28
 
B

b3ll3roph0n

:shock:

OK. Kontrollieren, ob ddclient läuft, kannst du mit
Code: 
ps aux | grep ddclient
oder schauen, ob das Pidfile (/var/run/ddclient.pid) existiert.

Dann würde ich an deiner Stelle die config etwas aufräumen ...
Ich bin kein Experte, was ddclient betrifft ...
... aber ich denke du solltest dich für eine Variante deine IP zu bestimmen entscheiden: use=...
Da du dich hinter einem Router befindest, entweder den Router abfragen
Code: 
use=D-link624+, fw=192.168.1.1:80
fw-login=admin, fw-password=XXXXXX
oder die IP via web bestimmen
Code: 
use=web
Wildcard ??
Code: 
wildcard=yes|no
wildcard=yes
Eine wildcard-Angabe reicht. Zudem der erste Eintrag auch falsch ist.

Die Serverkonfiguration kannst du imho auch zusammen fassen:
Code: 
login=************
password=******
server=members.dyndns.org
protocol=dyndns2
meineseite.dyndns.org
millerlite.dyndns.org
 
OP
J

James28

Hallo,

root 8410 0.0 0.0 2644 740 pts/4 R+ 19:04 0:00 grep ddclient

Was sagt mir das?

Die Datei /var/run/ddclient.pid existier nicht.

Wie starte ich denn dann den DDclient?

Gruß James28
 
B

b3ll3roph0n

Läuft also nicht ...
Starten solltest du den ddclient mit
Code: 
/etc/init.d/ddclient start
Zuerst solltest du aber mal festlegen, ob du ddclient als Daemon laufen lassen willst oder nur als ifup-Script.
Sollte sich in der /etc/default/ddclient einstellen lassen.
 
OP
J

James28

Hallo,

ich habe in der /etc/defauelt nix mit ddclient und der befehlt zum starten funzt auch nicht weil da scheinbar nix drinne ist.

Gruß James28
 
OP
J

James28

:? das kann ich dir garnicht mal sagen ich denke mal mein Kumpel hat den so installiert nach der anleitung:

===============================================================================
DDCLIENT v3.6.5

ddclient is a Perl client used to update dynamic DNS entries for accounts
on many dynamic DNS services.

IMPORTANT: The format and options used by ddclient have CHANGED.
Please examine the sample configuration file.
It is highly recommended that you take advantage of the
new daemon mode of operation.

IMPORTANT: The installation location for the ddclient script has changed from
/root/bin/
to
/usr/sbin/

===============================================================================

Dynamic DNS services currently supported include:

DynDNS.org - See http://www.dyndns.org for details on obtaining a free account.
Hammernode - See http://www.hn.org for details on obtaining a free account.
Zoneedit - See http://www.zoneedit.com for details.
EasyDNS - See http://www.easydns.com for details.
NameCheap - See http://www.namecheap.com for details

Also include is support for DSL Reports host monitoring service. [Highly recommended]
See http://dslreports.com for details.

DDclient now supports many of cable/dsl broadband routers.

Comments, suggestions and requests can always be sent to:
mailto:paul+ddclient@burry.ca

If you use ddclient, please send a brief note to:
mailto:paul+ddclient@burry.ca
and indicate if you would like to be notified of new releases.

.. Paul Burry

IMPORTANT UPDATE:
Paul doesn't maintain the code anymore. Everything is done through sf.net.
Please check out http://ddclient.sourceforge.net and the project page.

-------------------------------------------------------------------------------
REQUIREMENTS:

- one or more accounts from:
DynDNS.org - See http://www.dyndns.org for details on obtaining a free account.
Hammernode - See http://www.hn.org for details on obtaining a free account.
Zoneedit - See http://www.zoneedit.com for details.
EasyDNS - See http://www.easydns.com for details.
NameCheap - See http://www.namecheap.com for details

- Perl 5.004 or later

- Linux or probably any common Unix system

-------------------------------------------------------------------------------
INSTALLATION:

cp ddclient /usr/sbin/
mkdir /etc/ddclient
cp sample-etc_ddclient.conf /etc/ddclient/ddclient.conf
vi /etc/ddclient/ddclient.conf
-- and change hostnames, logins, and passwords appropriately

## For those using Redhat style rc files and using daemon-mode:
cp sample-etc_rc.d_init.d_ddclient /etc/rc.d/init.d/ddclient
## enable automatic startup when booting
/sbin/chkconfig --add ddclient
## start the first time by hand
/etc/rc.d/init.d/ddclient start

## If you are not using daemon-mode, configure cron and dhcp or ppp
## as described below.

-------------------------------------------------------------------------------
TROUBLESHOOTING:

1. enable debugging and verbose messages.
$ ddclient -daemon=0 -debug -verbose -noquiet

2. Do you need to specify a proxy?
If so, just add a
proxy=your.isp.proxy
to the ddclient.conf file.

3. Define the IP address of your router with fw=xxx.xxx.xxx.xxx in
/etc/ddclient/ddclient.conf and then try
$ ddclient -daemon=0 -query
to see if the router status web page can be understood.

4. Need support for another router/firewall?
Define the router status page yourself with:
fw=url-to-your-router's-status-page
fw-skip=any-string-preceding-your-IP-address

ddclient does something like this to provide builtin support for
common routers.
For example, the Linksys routers could have been added with:
fw=192.168.1.1/Status.htm
fw-skip=WAN.*?IP Address

OR
Send me the output from:
$ ddclient -geturl {fw-ip-status-url} [-login login [-password password]]
and I'll add it to the next release!

ie. for my fw/router I used:
$ ddclient -geturl 192.168.1.254/status.htm

5. Some broadband routers require the use of a password when ddclient
accesses its status page to determine the router's WAN IP address.
If this is the case for your router, add
fw-login=your-router-login
fw-password=your-router-password
to the beginning of your ddclient.conf file.
Note that some routers use either 'root' or 'admin' as their login
while some others accept anything.

-------------------------------------------------------------------------------
USING DDCLIENT WITH ppp

If you are using a ppp connection, you can easily update your DynDNS
entry with each connection, with:
## configure pppd to update DynDNS with each connection
cp sample-etc_ppp_ip-up.local /etc/ppp/ip-up.local

Alternatively, you may just configure ddclient to operate as a daemon
and monitor your ppp interface.

-------------------------------------------------------------------------------
USING DDCLIENT WITH cron

If you have not configured ddclient to use daemon-mode, you'll need to
configure cron to force an update once a month so that the dns entry will
not become stale.

## configure cron to force an update twice a month
cp sample-etc_cron.d_ddclient /etc/cron.d/ddclient
vi /etc/cron.d/ddclient

-------------------------------------------------------------------------------
USING DDCLIENT WITH dhcpcd-1.3.17

If you are using dhcpcd-1.3.17 or thereabouts, you can easily update
your DynDNS entry automatically every time your lease is obtained
or renewed by creating an executable file named:
/etc/dhcpc/dhcpcd-{your-interface}.exe
ie.:
cp sample-etc_dhcpc_dhcpcd-eth0.exe /etc/dhcpc/dhcpcd-{your-interface}.exe

In my case, it is named dhcpcd-eth0.exe and contains the lines:
#!/bin/sh
PATH=/usr/sbin:/root/bin:${PATH}
logger -t dhcpcd IP address changed to $1
ddclient -proxy fasthttp.sympatico.ca -wildcard -ip $1 | logger -t ddclient
exit 0

Other DHCP clients may have another method of calling out to programs
for updating DNS entries.

Alternatively, you may just configure ddclient to operate as a daemon
and monitor your ethernet interface.

-------------------------------------------------------------------------------
USING DDCLIENT WITH dhclient

If you are using the ISC DHCP client (dhclient), you can update
your DynDNS entry automatically every time your lease is obtained
or renewed by creating an executable file named:
/etc/dhclient-exit-hooks
ie.:
cp sample-etc_dhclient-exit-hooks /etc/dhclient-exit-hooks

Edit /etc/dhclient-exit-hooks to change any options required.

Alternatively, you may just configure ddclient to operate as a daemon
and monitor your ethernet interface.

-------------------------------------------------------------------------------
$Header: /cvsroot/ddclient/ddclient/README,v 1.8 2004/12/03 07:30:44 wimpunk Exp $

Gruß James28
 
OP
J

James28

Hi,

ich glaube ich habe es hinbekommen mit dem server habe einfach unter Yast den ddclient dienst hinzugefügt und schon lief das ding.

gruß James28
 
B

b3ll3roph0n

Tja, dann sollte dein "Kumpel" dir mal verraten, wie er den ddclient eingerichtet hat ...
... da ich meine Glaskugel gerade verlegt habe.

In der README sind nämlich so einige Varianten aufgeführt ...
- Als Daemon beim Systemstart starten
- Als ifup-Script bei jeder Einwahl (für Dialup-Verbindungen)
- Als cronjob
- Als Script beim Erneuern der dhcpd-leases

[edit]
Schön das es dann doch geklappt hat. :wink:
Wenn der Dienst über den Runlevel-Editor hinzugefügt werden kann, dann sollte aber auch ein Start-Script unter /etc/init.d vorhanden sein ...

Und markier den Thread bitte noch als "gelöst".
(Deinen ersten Beitrag editieren und ein [gelöst] zum Titel hinzufügen)
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Oben