Hello, Mark, Sproskin,
I've been able to update the dynamic DNS for a sub domain's IP address, but the sub domain name does not propagate:
<<
# traceroute 75.72.167.152
# traceroute to 75.72.167.152 (75.72.167.152), 64 hops max
1 10.12.0.1 90.548ms 94.324ms 91.668ms
2 67.215.234.65 89.336ms 90.486ms 91.622ms
3 96.44.180.1 89.892ms 89.175ms 91.164ms
4 129.250.201.49 93.480ms 91.096ms 90.241ms
5 129.250.2.221 90.295ms 90.517ms 91.318ms
6 50.242.151.61 94.244ms 91.435ms 89.944ms
....
>>
That's the IP address for lh2.friendsofulc.org. But:
<<
# traceroute lh2.friendsofulc.org
traceroute: unknown host
>>
Following your advice, I used https://www.whatsmydns.net/ to check for propagation:
www. (as either A Name or C Name) gets green checks all down
blog. (A or C) green all the way down
lh2. (Is a DDNS sub a C, A, or Alias?) red x's all down.
The control panel on zoneedit.com shows the IP next to that sub domain. The root domain is not resolved, but two sub domains on the root have resolved with no problem for years (blog. and www.)
The updater is running fine, which it has to be to give the sub domain that IP address (ez-ipupdate on a FreeBSD server). I don't think I can fix a propagation problem? That has to be done on your end, correct?
Thanks,
Gordon
I've been able to update the dynamic DNS for a sub domain's IP address, but the sub domain name does not propagate:
<<
# traceroute 75.72.167.152
# traceroute to 75.72.167.152 (75.72.167.152), 64 hops max
1 10.12.0.1 90.548ms 94.324ms 91.668ms
2 67.215.234.65 89.336ms 90.486ms 91.622ms
3 96.44.180.1 89.892ms 89.175ms 91.164ms
4 129.250.201.49 93.480ms 91.096ms 90.241ms
5 129.250.2.221 90.295ms 90.517ms 91.318ms
6 50.242.151.61 94.244ms 91.435ms 89.944ms
....
>>
That's the IP address for lh2.friendsofulc.org. But:
<<
# traceroute lh2.friendsofulc.org
traceroute: unknown host
>>
Following your advice, I used https://www.whatsmydns.net/ to check for propagation:
www. (as either A Name or C Name) gets green checks all down
blog. (A or C) green all the way down
lh2. (Is a DDNS sub a C, A, or Alias?) red x's all down.
The control panel on zoneedit.com shows the IP next to that sub domain. The root domain is not resolved, but two sub domains on the root have resolved with no problem for years (blog. and www.)
The updater is running fine, which it has to be to give the sub domain that IP address (ez-ipupdate on a FreeBSD server). I don't think I can fix a propagation problem? That has to be done on your end, correct?
Thanks,
Gordon