I am trying to configure TZO DDNS on my 1941. The DDNS lines in the configuration file were provided one year ago by TZO support for a 1811W router, which was working befor i migrated to the 1941. I have attached a config file and a debug file. The unusual part of the debug file is session id 0x95. I thnk this is the format the router would use if it had been configured using CCP. I had tried CCP initially but it didnt work, so I deleted it from the configuration and used CLI instead. Session ID 0x96 is the call the router is making using the CLI configuration, as seen in the attached config file.
I am not sure where the problem is here. it appears to be logging on to TZO. It also appears that the router name is being added to the logon ID in session 0x95...ie instead of myname.net the router is sending cisco1941.myname.net ---not sure if this is relevant or not. It also appears that the update happens? At least that'w what I can garner from the log file.
I contacted engineering at TZO - and this was their suggestions:
So what is happening is the cisco ddns client is prepending the hostname "hostname cisco1941" to the ddns update method name. When we see the update come in the name doesn't match what we have in our database. we have "myname.net" and the ddns update has "cisco1941.myname.net" so it fails.
One possibility is the removal of client-id from the DHCP conf string for G0/0
change "ip address dhcp client-id GigabitEthernet0/0" to "ip address dhcp" or "ip address dhcp GigabitEthernet0/0".
This might alter the update name so it doesn't pass the units hostname with the ddns update.
ip ddns update TZO
ip address dhcp client-id GigabitEthernet0/0
ip nat outside
no cdp enable
no mop enabled
Another possible config to try is to change the hostname of the router to "myname", by doing this the ddns update method will see the names are same and drop the hostname and just use what is in the ddns update method. If it happens that it prepends myname to myname.net and we get myname.myname.net you can try removing the hostname altogether.
Please let me know how you make out.
unfortunately, none of these worked out. The ip address dhcp client-id changes were not recognized by IOS and the hostname changes dis not work, in fact, got router prepended to the logon id
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...