Please refresh slack.com DNS record

[totsilence]

Dear Vodafone Team,

At the moment slack.com can not be reached because of:

https://twitter.com/SlackHQ/status/1443686542665453572?ref_src=twsrc%5Etfw

It would be great if the DNS record could be refreshed, as it is a vital tool for many in homeoffice.

[Stephan871]

I have the same issue today. 

I could solve it meanwhile via using the company VPN. But I also hope that Vodafone updates their DNS soon.

[reneromann]

Vodafone doesn't refresh any DNS records - that is done after the "old" (and wrong) record times out...

And as Slack stated: They made the mistake and thus it'll take time to resolve - nothing that Vodafone could do about it.

[Kieferer]

For shure, it is a VF problem.

By default there isn't any DNS update service. You may have a look at root name servers. How VF handle their censorshiped DNS Servers I don't know. But there is a remarkable outage in VF DNS or limited services.

My resolver for slack.com get a result, so no problem at all. In my setup IPv6 is not in use.

Mehr anzeigen

COMMUNITY EDITION
DiagnosticsDNS Lookup
DNS Lookup
Hostname
slack.com
Results
Result	Record type
3.123.248.34	A
Timings
Name server	Query time
127.0.0.1	163 msec
5.9.164.112	65 msec
176.9.93.198	24 msec
89.233.43.71	24 msec
95.216.24.230	24 msec
185.49.141.37	24 msec
145.100.185.17	22 msec
145.100.185.18	24 msec
185.222.222.222	24 msec
146.255.56.98	23 msec
140.238.215.192	23 msec
185.95.218.42	23 msec
158.64.1.29	23 msec
81.3.27.54	23 msec
More Information
Ping
Traceroute
pfSense is developed and maintained by Netgate. © ESF 2004 - 2021 View license.

The question is why a dozens of DNS servers are working fine and VF won't.

[reneromann]

If Slack publishes a wrong DNS entry - as they did according to their tweet - then Vodafone can't do anything about it. The "wrong" DNS entry has a lifespan and there's no need to renew any DNS entry within this lifespan - that's why if a DNS server was fetching this "wrong" DNS entry, it will have that wrong entry in its cache until the caching time (which is also set by the DNS entry owner in its original record) has passed.

As the lifespan is usually set to be one day, it'll "self-heal" one day after the malicious entry has been fixed. But this has nothing to do with Vodafone but is how DNS caching works by purpose. And if Slack publishes a malicious DNS entry, than its only their responsibility to correct their mistake - Vodafone and other providers aren't able to do anything about it.

[Kieferer]

As noted, I'm running in pure IPv4 in Bridge Mode. Slack may have a IPv6 problem. IPv4 is working fine. Check it out at internet.nl

Edith: VF Mobile resolves slack.com like a charm.