EDIT:
shame on me ... deployed host with sum with static old ip :-(
everything works now... redirected the requests going to the old ip to the new ip and now deployed the correct ip
what a shame ... sorry @all
Hi all,
I encountered this problem, too
i've set up dns-host definitions for our sum server on each customer utm.
like so:
now i've changed the dns for sum.company.com from A.A.A.A to B.B.B.B at the dns hoster...
All (there are a lot) customer UTM didn't recognize the change in the public dns and they all do have the old A.A.A.A IP in their cache.
I think this is some kind of bug...
BAlfson... do you have an idea what i can do to make my customer umts update their dns cache ?
Cheers,
Chris
EDIT:
shame on me ... deployed host with sum with static old ip :-(
everything works now... redirected the requests going to the old ip to the new ip and now deployed the correct ip
what a shame ... sorry @all
Hi all,
I encountered this problem, too
i've set up dns-host definitions for our sum server on each customer utm.
like so:
now i've changed the dns for sum.company.com from A.A.A.A to B.B.B.B at the dns hoster...
All (there are a lot) customer UTM didn't recognize the change in the public dns and they all do have the old A.A.A.A IP in their cache.
I think this is some kind of bug...
BAlfson... do you have an idea what i can do to make my customer umts update their dns cache ?
Cheers,
Chris
Hallo Chris,
You can do this at the command line with:
cc dns_flush_cache
Or, in WebAdmin, at the bottom of the 'Global' tab in 'DNS'.
Depending on the TTL in the authoritative name server, it still may take awhile for their internal devices to refresh.
Cheers - Bob