Last Modified Date: 15 Jan 2019
Environment
- Tableau Online Dub01
- Authentication
- DNS
Resolution
- Clear your web browsers cache, try incognito mode, and or other web browsers.
- Verify the DNS cache has been flushed on your machine. See How To Clear Your DNS Cache for more information.
- If your companies network has a DNS server, flush the DNS cache from the IT network level.
Cause
The Dub01 pod has been migrated from on-premises servers to AWS.Additional Information
To verify whether your network has a server caching the old DNS entries for Tableau Online, follow the below steps.- Run the Windows Command Prompt as an administrator, and execute the below command.
- nslookup dub01.online.tableau.com
- Check whether if the DNS results are being returned by a server within your network.
- Below is an example of cached DNS results being returned within a local network.
- C:\WINDOWS\system32>nslookup dub01.online.tableau.com
Server: mycompanynetwork.lan
Address: 10.0.0.x
Non-authoritative answer:
Name: e7144.g.akamaiedge.net
Address: 172.226.189.50
Aliases: dub01.online.tableau.com
dub01.online.tableau.com.edgekey.net
- C:\WINDOWS\system32>nslookup dub01.online.tableau.com
- Execute the below command to see if different DNS results are returned by a public DNS server.
- nslookup dub01.online.tableau.com 8.8.8.8
- If the initial results from Step 3 are different than the above and are returned by a server within your network, work with your IT team to flush the DNS cache at the server indicated in the initial results.
Discuss this article... Feedback Forum
Thank you for providing your feedback on the effectiveness of the article.
Open new Case
Continue Searching
Knowledge Base
Community
Product Help
Training and Tutorials