You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on this story Set domain nameservers (#167822556 for us) We spent a decent amount of time trying to use the dig command for the expected result only to find we were digging in the wrong place. We think bolding the "your" in the expected results would make it apparent that you should switch back to your machine.
When you get back, go to your GCP Cloud DNS entry. Find the IP associated with *.your-domain.com. Running dig api.your-domain.com should return the same IP address.
The text was updated successfully, but these errors were encountered:
While working on this story
Set domain nameservers
(#167822556
for us) We spent a decent amount of time trying to use the dig command for the expected result only to find we were digging in the wrong place. We think bolding the "your" in the expected results would make it apparent that you should switch back to your machine.When you get back, go to your GCP Cloud DNS entry. Find the IP associated with *.your-domain.com. Running dig api.your-domain.com should return the same IP address.
The text was updated successfully, but these errors were encountered: