I'd recommend for machines attempting to access Plivo services (servers or
desktops) to use static entries in your /etc/hosts files (Linux/Unix
servers, MacOS) or your C:\Windows\System32\Drivers\etc\hosts file
(Windows).
https://www.petri.com/easily-edit-hosts-file-windows-10
https://linux.die.net/man/5/hosts
I added this line to my /etc/hosts file on servers needing to access Plivo
servers statically (I only use the API):
54.183.118.182 api.plivo.com
Now working for me.
If you try to use the IP, you'll get a 301 HTTP Redirect to the named host,
which will obviously fail. They need to change the HTTP server config to
not do that, so right now the fastest way to get access back is through
static entries on the servers that need to talk to Plivo.
Beckman
On Sun, 23 Apr 2017, Peter Beckman wrote:
Looks like they are calling it a "DNS" issue -- not sure they noticed that
their whois record expired and the root servers are using NOT their DNS
servers to resolve plivo.com domains.
https://docs.google.com/document/u/1/d/1hHIGcDQYb7nlL09-K1IOG_6mnVSDIHw_7D62X9RAneE/pub
I wonder if it might be faster or them to get an alternative domain up as a
stop-gap...
Description
We are experiencing an issue with DNS resolution of plivo.com domains
due to a registrar renewal expiration. We are actively working on it.
We recommend all our customers to use google DNS 8.8.8.8 and 8.8.4.4
for the following domains: api.plivo.com, phone.plivo.com,
app.plivo.com, manage.plivo.com, sbc.plivo.com, eu.sbc.plivo.com,
asia.sbc.plivo.com, au.sbc.plivo.com, sa.sbc.plivo.com
Note: Other DNS resolvers may work as soon as the DNS for plivo.com are
propagated but we cannot guarantee the TTL (refresh time) as it is out
of our control.
We apologize for the inconvenience, we are doing our best to get the
service back.
Recommended resolution: You can hardcode the following DNS entries
while we are working on resolving the issue.
Last update : Sun Apr 23 15:07:56 UTC 2017
DNS name
IPs
api.plivo.com
52.8.14.77
54.183.118.182
manage.plivo.com
54.215.176.31
52.8.129.90
app.plivo.com
54.241.31.73
phone.plivo.com
98.158.107.18
sbc.plivo.com
54.235.170.44
eu.sbc.plivo.com
54.247.99.121
asia.sbc.plivo.com
54.251.107.105
au.sbc.plivo.com
54.253.253.59
sa.sbc.plivo.com
54.233.255.206
Events
Sun Apr 23 14:18:48 UTC 2017
While we are working with our DNS provider for plivo.com, we are
currently deploying an alternative solution to get the service back online.
Sun Apr 23 13:22:10 UTC 2017
We are working with our provider to expedite the renewal of the DNS.
We will update you shortly.
Might want to watch that Google Doc for updates
Beckman
On Sun, 23 Apr 2017, Peter Beckman wrote:
We use Plivo as a monitoring tool for SMS. They've been rock-solid and
reliable, and did a good job of letting people know if things were broken.
Their domain expired on April 17th, and now everything in their network is
unreachable, including their status.plivo.com site.
Is there anyone from Plivo on the list that cares to comment? There isn't
anything on Twitter (@plivo) mentioning that they are aware of the
situation and working on it, which concerns me. We started noticing issues
mid-last week, but didn't dig into it (clearly should have).
While their disappearance isn't affecting our customers, we have lost
visibility of our off-net to on-net SMS testing.
---------------------------------------------------------------------------
Peter Beckman Internet Guy
[email protected] http://www.angryox.com/
---------------------------------------------------------------------------
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
---------------------------------------------------------------------------
Peter Beckman Internet Guy
[email protected] http://www.angryox.com/
---------------------------------------------------------------------------
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
