Attachment 3799 Details for Bug 24604

Zu migrierende Dokumentation

ddns_en.tex (text/x-tex), 2.62 KB, created by Moritz Muehlenhoff on 2011-11-14 16:38 CET

(hide)

Description:

Filename:

MIME Type:

Creator: Moritz Muehlenhoff

Created: 2011-11-14 16:38 CET

Size: 2.62 KB

patch

obsolete

>\begin{ucsTabbox}{'[DHCP Dynamic DNS]' tab}
>Settings for dynamic DNS updates can be performed on this tab. For
>technical reasons these cannot yet be performed with a UCS-based DNS
>service, but only with external servers.
>
>\ucsTabentry{DDNS hostname}
>As standard, the DHCP service uses the computer name delivered from
>the client for DDNS updates. If a string is entered in this input
>field, this is used instead of the delivered computer name.
>
>\ucsTabentry{DDNS domain name}
>The domain name entered here is used together with the client's
>computer name to compile a fully qualified domainn name.
>
>\ucsTabentry{DDNS reverse domain name}
>The domain name entered here is hung onto a reversed IP address to
>compose a name for a pointer record (PTR record). If no domain name is
>entered, the standard value \emph{in-addr.arpa.} is used.
>
>\ucsTabentry{DDNS updates}
>If this setting is set to \ucsMenuEntry{on}, the DHCP service attempts
>a DNS update if a lease is confirmed. No update is performed when
>\ucsMenuEntry{off} is selected. The standard setting is
>\ucsMenuEntry{on}.
>
>\ucsTabentry{DDNS update style}
>There are currently two DNS update patterns available: the ad-hoc DNS
>update mode (\ucsMenuEntry{ad-hoc}) and the interim DHCP-DNS
>interaction draft update mode (\ucsMenuEntry{interim}). 
>The \ucsMenuEntry{ad-hoc} mode is now outdated and should no longer be
>used.
>\ucsNote{This setting is evaluated once by the DHCP service when
>  importing the configuration. It is thus not possible to stipulate
>  the update style for each client individually.}
>
>\ucsTabentry{DDNS Forward Updates}
>If the \ucsMenuEntry{True} value is selected, the DHCP service updates
>the DNS computer entry (A record) if a DHCP client requests or renews
>a lease. No update is performed if the setting is set to
>\ucsMenuEntry{false}. This input only applies when DNS updates are
>activated and the \ucsMenuEntry{DDNS update style} is set to
>\ucsMenuEntry{interim}. DDNS forward updates are performed as
>standard.
>
>\ucsTabentry{Update static leases}
>If the \ucsMenuEntry{True} value is selected, the DHCP service
>performs DNS updates, even when they are assigned a static IP
>address. No update is performed if the setting is set to
>\ucsMenuEntry{false}. This input only applies when DNS updates are
>activated and the \ucsMenuEntry{DDNS Update Stil} is set to
>\ucsMenuEntry{interim}.
>
>\ucsTabentry{Client updates}
>When the \ucsMenuEntry{Allow} value is selected, the DHCP service
>notes the intention of the DHCP client to update its own DNS
>computer entry (A record). This input only applies when DNS updates
>are activated and the \ucsMenuEntry{DDNS Update Stil} is set to
>\ucsMenuEntry{interim}.
>\end{ucsTabbox}

Actions: View

Attachments on bug 24604: 3796 | 3797 | 3798 | 3799 | 3800 | 3801