<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 2018-01-19 10:20 AM, K5CG wrote:<br>
<blockquote type="cite"
cite="mid:722470462.1332.1516375211677.JavaMail.zimbra@siminiuk.com">
<div style="font-family: tahoma,new york,times,serif; font-size:
12pt; color: #000000">
<div>Ramesh,</div>
<div><br data-mce-bogus="1">
</div>
<div>Until your pi can resolve the address correctly (for
whatever reason) it's still a problem.</div>
<div><br data-mce-bogus="1">
</div>
<div>Does "ping stats.allstarlink.org" return the new address or
the old?</div>
<div><br data-mce-bogus="1">
</div>
<div>Does it resolve correctly from another PC on your LAN? etc.</div>
<div><br data-mce-bogus="1">
</div>
<br>
</div>
</blockquote>
<-- Hi Danny: a ping from the Pi still returns the old
(209.x.x.x) address; I rebooted the Pi to ensure any cached DNS
entries get flushed. I've just logged into my D-STAR system on the
same network (so NAT'd behind the same router) and get the same
issue. So perhaps the DNS changes have not propagated through.
I'll wait a little longer and, if needed, I'll hard-code the change
in my host file to force the new IP... until the DNS changes
catch-up.<br>
<br>
Cheers,<br>
<br>
Ramesh.<br>
</body>
</html>