This section provides a sample of configuring DNS using the edit-config:merge method.
Operation |
XPATH |
|---|---|
edit-config:merge |
/ietf-system:system/dns-resolver |
Data Requirements
Item |
Data |
Description |
|---|---|---|
DNS server name |
t2 |
- |
DNS server address. |
192.168.1.5 |
- |
Request Example
<?xml version='1.0' encoding='UTF-8'?>
<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<sys:system xmlns:sys="urn:ietf:params:xml:ns:yang:ietf-system">
<sys:dns-resolver>
<sys:server>
<sys:name>t2</sys:name>
<sys:udp-and-tcp>
<sys:address>192.168.1.5</sys:address>
</sys:udp-and-tcp>
</sys:server>
</sys:dns-resolver>
</sys:system>
</config>
</edit-config>
</rpc>
Response Example
Sample of successful response
<?xml version='1.0' encoding='UTF-8'?> <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="35"> <ok/> </rpc-reply>
Sample of failed response
<?xml version='1.0' encoding='UTF-8'?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="36">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-message>parse rpc config error.</error-message>
</rpc-error>
</rpc-reply>