How to enable DYN DNS on MAS

Introduction :

 

Dynamic DNS Client enables the switch to update its public facing IP address with the public domain DDNS server. This avoids the user from  having to manually login to the DNS server and update the IP address.

 

Feature Notes :

 

 

* DDNS client is disabled on the switch by default.
* DDNS client can be configured on the Mobility Access switch by mapping it to RVI profile
* DDNS profile can be attached to an RVI which gets IP using DHCP
* “ip name-server” has to be configured on switch
* Only two  DDNS profiles can be created on switch
* Only one DDNS profile can be attached per RVI

 

 

Environment :

 

This article applies to product - Mobility access switches running code 7.4.0.0 and above

 

Network Topology :

 

Network with Mobility access switches with public domain DNS server

 

Configuration Steps :

 

 

Create DDNS profile
 
DDNS-CLIENT) (config) #interface-profile ddns-profile test
(DDNS-CLIENT) (DDNS profile "test") #username test-dyndns1
(DDNS-CLIENT) (DDNS profile "test") #password ARUBA.123
(DDNS-CLIENT) (DDNS profile "test") #service-url dynupdate.no-ip.com/nic/update
(DDNS-CLIENT) (DDNS profile "test") #hostname test-dyndns.ddns.net
(DDNS-CLIENT) (DDNS profile "test") #exit
 
Attach the created DDNS profile to RVI
(DDNS-CLIENT) (config) #interface vlan 196
(DDNS-CLIENT) (vlan "196") #ddns-profile test
 

 

Answer :

 

 

The client associated with a domain name, gets a dynamic IP address from the DHCP server. With Dynamic DNS, the client automatically updates the change in the IP address to the Domain Name to which it is mapped.

 

 

 

This avoids the user from  having to manually login to the DNS server and update the IP address.Dynamic DNS Client enables the switch to update its public facing IP address with the public domain DDNS server. 

 


DDNS client can be configured on the Mobility Access switch using CLI as follows,
 Create DDNS profile
 Attach DDNS profile to RVI
 

 

Verification :

 

 

DDNS-CLIENT) #show interface-profile ddns-profile test

 

 

 

DDNS profile "test" (N/A)

 

-------------------------

 

Parameter                           Value

 

---------                           -----

 

Configured update interval [D:H:M]  7:0:0

 

Configured username                 test-dyndns1

 

Configured password                 ********

 

Configured service-url              dynupdate.no-ip.com/nic/update

 

Configured hostname                 test-dyndns.ddns.net

 

 

 

 

 

(DDNS-CLIENT) #show interface-profile ddns-profile

 

 

 

DDNS profile List

 

-----------------

 

Name   References  Profile Status

 

----   ----------  --------------

 

dyn-1  0           N/A

 

test   1           N/A

 

Total:2

 

 

 

(DDNS-CLIENT) #show ddns-client

 

 

 

Dynamic DNS Client Information

 

------------------------------

 

Interface  Hostname              Service URL                     IP Address

 

---------  --------              -----------                     ----------

 

vlan196    test-dyndns.ddns.net  dynupdate.no-ip.com/nic/update  196.168.10.62
 
Troubleshooting :
 
Enable traces to  the see DDNS updates sent from  switch.
DDNS-CLIENT) (config) #traceoptions
(DDNS-CLIENT) (traceoptions) #ddns flags all
 
DDNS updates can be checked from  the traces
(DDNS-CLIENT) (config) #show trace ddns 10
 
Jul 23 19:56:56 [DDNS] DDNS update add called for test-dyndns.ddns.net h_name with IP: 196.168.10.62
Jul 23 19:56:56 [DDNS-SENT] sending request...
Jul 23 19:56:56 [DDNS-RECV] return value: 0
Jul 23 19:56:56 [DDNS-SENT] ***Transfer succeeded***
Jul 23 19:56:56 [DDNS-RECV] The response is: good 196.168.10.62
Jul 23 19:56:56 [DDNS-TIMER] DDNS task_timer called timer_name : DDNS_TIMER_vlan196
Jul 23 19:56:56 [DDNS] DDNS task_timer created with timeout value: 604800
 
***Transfer succeeded*** indicates that  the update was sent successfully to DDNS server
 
 
Response codes  common  for  most  service-providers
 
Status    Success/Error  Description
Good       Success            DNS hostname update successful
Nochg      Success             ip address is current, no update performed
Nohost      Error               Hostname supplied does not exist under specified account
Badauth     Error               Invalid user name and password combination
911          Error               A fatal error on our side such as a database outage

 

Version history
Revision #:
1 of 1
Last update:
‎11-11-2014 06:12 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.