Configuring the DNS update service

Article:HOWTO60436  |  Created: 2011-10-20  |  Updated: 2012-02-03  |  Article URL http://www.symantec.com/docs/HOWTO60436
Article Type
How To


Environment

Subject


Configuring the DNS update service

Use the DR> dnsupdate set command to configure the DNS update service parameters.

You can configure DNS update service parameters on a cluster only when the DNS update service is offline for the cluster. The parameter changes take effect when the DNS update service is started.

To set the DNS server

  • To set the DNS server where configuration information is uploaded, enter the following:

    DR> dnsupdate set dns_server ip_address

    where ip_address is the IP address of the DNS server.

    For example:

    DR> dnsupdate set dns_server 172.10.409.251
    SFS DNSupdate SUCCESS V-288-0 operation dnsserver 172.10.409.251 
    successful on cluster1.

To set the domain name

  • To set the domain name that is associated with the DNS server, enter the following:

    DR> dnsupdate set domain_name domain_name

    where domain_name is the domain name. This domain specifies the service that is hosted on the cluster. Clients use the domain name to access the cluster's service.

    For example:

    DR> dnsupdate set domain_name sfs.example.com
    SFS DNSupdate SUCCESS V-288-0 operation domain_name 
    sfs.example.com successful on cluster1.

To set the keyfiles path

  • To set the path to the TSIG key files for the DNS server, enter the following:

    DR> dnsupdate set keyfiles scp-URL filename.key filename.private

    scp-URL

    Indicates the SCP URL where the key files are stored for the DNS server.

    The TSIG key files are a pair of files that are generated by the DNS server administrator. They are used for making secure updates to the DNS server. One file in the pair has a *.key extension. The other file has a *.private extension.

    filename.key

    Indicates the file name for the *.key TSIG file.

    filename.private

    Indicates the file name for the *.private TSIG file.

    For example:

    DR> dnsupdate set keyfiles scp://lkarnes@mkt1:/secure/ 
    Kexample.com.+157+20648.key Kexample.com.+157+20648.private
    Password:*******
    SFS DNSUpdate SUCCESS V-288-0 operation keyfile 
    Kexample.com.+157+20648.private successful on cluster1.

To add a replication link to the DNS update configuration

  • To add a replication link to the DNS update configuration, enter the following:

    DR> dnsupdate addreplink link_name

    where link_name is the name of a replication link.

    The DR> dnsupdate set addreplink command does not create a replication link, instead it configures the specified replication link with the same DNS update parameters as on the local cluster.

    For example:

    DR> dnsupdate addreplink Rep1
    SFS DNSUpdate SUCCESS V-288-0 operation addreplink Rep1
    successful on cluster1.

    When you add a replication link to the DNS update configuration, existing parameters for the DNS update service are set on both the local and the remote cluster.

    For example:

    SFS DNSupdate SUCCESS V-288-0 operation dnsserver 
    172.10.409.251 successful on cluster2.
    SFS DNSupdate SUCCESS V-288-0 operation domain_name 
    sfs.example.com successful on cluster2.
    SFS DNSUpdate SUCCESS V-288-0 operation keyfile 
    Kexample.com.+157+20648.private successful on cluster2.
    SFS DNSUpdate SUCCESS V-288-0 operation keyfile 
    scp://lkarnes@mkt1:/secure/ successful on cluster2.

To delete a replication link from the DNS update configuration

  • To delete a replication link to the DNS update configuration, enter the following:

    DR> dnsupdate delreplink link_name

    where link_name is the name of a replication link.

    The DR> dnsupdate set delreplink command does not delete a replication link, instead it removes the link from the DNS update configuration.

    For example:

    DR> dnsupdate delreplink Rep1
    SFS DNSUpdate SUCCESS V-288-0 operation delreplink Rep1
    successful on cluster1.

Legacy ID



v58677435_v64777215


Article URL http://www.symantec.com/docs/HOWTO60436


Terms of use for this information are found in Legal Notices