I've found this article is at http://www.fir3net.com/Juniper-Netscreen/netscreen-ddns-last-response-not-init.html it explains how to resolve the 'not init' issue while attempting to start DynDNS client on a Netscreen
The below is based on the netscreen ns5gt and the firefox web browser.
Issue
After setting up your netscreen for DDNS, in the UI of your netscreen the last response is shown as 'not-init' and within the CLI it shows 'successful updates: 0'.
To get the id of you ddns config run just the command `get dns ddns` via the CLI.
ns5gt-> get dns ddns id 209
Id: 209
State: Init
Socket: -1
Type: dyndns
Server: members.dyndns.org
Clear-text: no
Refresh-int: 3 days 14 hours 0 minutes 0 seconds
Min-update-int: 2 hours 0 minutes 0 seconds
Next-update: 1 minutes 0 seconds
Username: ******
Password: **********
Agent: Netscreen-6.2.0r1.0-0064032004004624
Src-interface: ethernet3
Host-name: *****.dyndns.net
Last-response: not-init
Last-response-ip: 0.0.0.0
Counters
--------------------------------------------------------------------------------
Successful updates: 0
Failed updates: 0
Server lookup failures: 0
Socket creation errors: 0
Socket connect errors: 2
Socket send errors: 0
Resolution
This is normally down to the netscreen not having the required Certificate installed. These are the steps,
- Go to the website https://members.dyndns.org/ and double click the padlock.
- Click View Certificates, click the details tab, click the Certificate Hierarchy of Equifax Secure CA
- Click Export and then save the certificate.
- Go into the Web UI of the Netscreen and go to objects, Certificates, and upload.
- Go back to the DDNS section and click refresh.
- You should now see from the output of get dns ddns that it has successfully updated.
No comments:
Post a Comment