From: "Thomas Walter" <thomas.walter@csc-online.eu>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] nsupdate
Date: Wed, 28 Jan 2015 15:41:44 +0100 [thread overview]
Message-ID: <005301d03b08$896ddc80$9c499580$@csc-online.eu> (raw)
In-Reply-To: <915054555B5659448ACF8A70E114824D01984A2481@Exchange2010.kamstrup.dk>
Hi Bruno,
Thanks for the info, so I did not oversee something ... good.
I looked briefly into the DNSUtils and it seems that there are a lot of
dependencies in regard to required libraries, etc.
Would be great if you could share some of your findings and progress on
that. For now I probably use the dnsutils on the DNS server and trigger
updates otherwise from my device instead of invoking an nsupdate directly.
Thx a lot in advance,
Tom
-----Original Message-----
From: ptxdist-bounces@pengutronix.de [mailto:ptxdist-bounces@pengutronix.de]
On Behalf Of Bruno Thomsen
Sent: Mittwoch, 28. Januar 2015 08:37
To: ptxdist@pengutronix.de
Cc: thomas.walter@csc-online.eu
Subject: Re: [ptxdist] nsupdate
Hi Tom,
> I am currently working on a kind of dyndns approach and plan to use
nsupdate to make the ddns aware of the new IP. However, it seems that
nsupdate is missing in ptxdist. Is this the case or do I miss something in
the configuration to enable it?
Yes, there are currently no rule to install nsupdate that is part of Bind.
I also needs to update DNS records automatically and was planning to create
a rule that compile and install DNS client tools from Bind 9.
/Bruno
--
ptxdist mailing list
ptxdist@pengutronix.de
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-01-28 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 15:14 Thomas Walter
2015-01-28 7:36 ` Bruno Thomsen
2015-01-28 14:41 ` Thomas Walter [this message]
2015-01-28 19:11 ` Uwe Kleine-König
2015-01-29 6:24 ` Thomas Walter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005301d03b08$896ddc80$9c499580$@csc-online.eu' \
--to=thomas.walter@csc-online.eu \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox