1. Home
  2. Cisco Systems
  3. Dynamic DNS woes

Dynamic DNS woes

I've been trying to get Dynamic DNS to work on my router for some time now.

Here is the debug transcript:

millcorner#

*Dec 20 16:18:06.275: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down *Dec 20 16:18:06.279: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di0 *Dec 20 16:18:06.283: DYNUPD: SWIF goingdown 'Virtual-Access2' *Dec 20 16:18:06.291: DYNDNSUPD: Removing DNS mapping for millcorner.ath.cx 85.210.23.196 *Dec 20 16:18:06.291: HTTPDNS: Update remove called for millcorner.ath.cx 85.210.23.196 *Dec 20 16:18:06.295: HTTPDNSUPD: Session ID = 0x7 *Dec 20 16:18:06.295: HTTPDNSUPD: URL = 'http://jchajecki: snipped-for-privacy@members.dyndns.org/nic/update?system=dyndns&hostname=millcorner.ath.cx&myip=85.210.23.196' *Dec 20 16:18:06.295: HTTPDNSUPD: Sending request *Dec 20 16:18:07.239: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up *Dec 20 16:18:07.243: %DIALER-6-BIND: Interface Vi2 bound to profile Di0 *Dec 20 16:18:07.279: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down *Dec 20 16:18:15.063: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up *Dec 20 16:18:15.063: DYNUPD: SWIF comingup 'Virtual-Access2' *Dec 20 16:18:26.307: HTTPDNSUPD: Call returned Connection time out for update millcorner.ath.cx 85.210.23.196 *Dec 20 16:18:26.307: DYNDNSUPD: Another update completed (outstanding=0, total=0) *Dec 20 16:18:26.315: HTTPDNSUPD: Clearing all session 7 info *Dec 20 16:18:27.331: DYNDNSUPD: Adding DNS mapping for millcorner.ath.cx 85.210.39.210 *Dec 20 16:18:27.331: DYNDNSUPD: Sleeping for 3 seconds waiting for interface Dialer0 configuration to settle *Dec 20 16:18:30.331: HTTPDNS: Update add called for millcorner.ath.cx 85.210.39.210 *Dec 20 16:18:30.331: HTTPDNSUPD: Session ID = 0x8 *Dec 20 16:18:30.331: HTTPDNSUPD: URL = 'http://jchajecki: snipped-for-privacy@members.dyndns.org/nic/update?system=dyndns&hostname=millcorner.ath.cx&myip=85.210.39.210' *Dec 20 16:18:30.331: HTTPDNSUPD: Sending request *Dec 20 16:18:40.339: HTTPDNSUPD: Call returned Request Aborted for update millcorner.ath.cx 85.210.39.210 *Dec 20 16:18:40.339: DYNDNSUPD: Another update completed (outstanding=0, total=0) *Dec 20 16:18:40.343: HTTPDNSUPD: Clearing all session 8 info millcorner#

Sometimes I get Request Aborted as above. Other times I get request timed out. Why does this keep happening.

"Sleeping for 3 seconds waiting for interface Dialer0 configuration to settle"

Is it possible to increase the 'sleep' interval to say 10 seconds? Might this help?

Reply to
John Chajecki
Loading thread data ...

John Chajecki schrieb:

85.210.23.196

'http://jchajecki: snipped-for-privacy@members.dyndns.org/nic/update?system=dyndns&hostname=millcorner.ath.cx&myip=85.210.23.196'

Virtual-Access2, changed state to down

Virtual-Access2, changed state to up

millcorner.ath.cx 85.210.23.196

Dialer0 configuration to settle

'http://jchajecki: snipped-for-privacy@members.dyndns.org/nic/update?system=dyndns&hostname=millcorner.ath.cx&myip=85.210.39.210'

millcorner.ath.cx 85.210.39.210

Allow access from tcp members.dyndns.org eq 80 in your WAN side inbound access-list.

Reply to
Uli Link

I have already provided this. My inboud list has the following entry:

access-list 103 permit tcp host 63.208.196.95 any eq www

Originally entered as access-list 103 permit tcp members.dyndns.org any eq www but the router seems to have resolved and substituted the IP address.

Reply to
John Chajecki

John Chajecki schrieb:

but the router seems to have resolved and substituted the IP address.

"access-list 103 permit tcp host 63.208.196.95 eq www any"

The http requests originates from the WAN interface, so CBAC does not add a dynamic ACE.

Reply to
Uli Link

Solved it!

The access list entry should have been:

access-list 103 permit tcp host 63.208.196.95 eq www any

NOT

access-list 103 permit tcp host 63.208.196.95 any eq www

as I originally had it.

The 837 would initiate a request TO port 80 of the DDNS server using a random source port. I needed to allow return traffic FROM port 80 of the DDNS server back to the originating source port ('any' since the source port is selected at random) of the 837.

I had inadvertantly reversed the order of the source and destination ports.

Reply to
John Chajecki

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.