From fb8690529f8ef882ab0cde587b1130ab35ce8f2d Mon Sep 17 00:00:00 2001 From: Ludovico Magnocavallo Date: Thu, 16 Apr 2020 09:07:16 +0200 Subject: [PATCH] fixes onprem example docs --- infrastructure/onprem-google-access-dns/README.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/infrastructure/onprem-google-access-dns/README.md b/infrastructure/onprem-google-access-dns/README.md index 39f7a6d8..2820c8f5 100644 --- a/infrastructure/onprem-google-access-dns/README.md +++ b/infrastructure/onprem-google-access-dns/README.md @@ -44,7 +44,7 @@ If the forwader address does not match the Terraform variable, add the correct v ```bash tf apply -tf taint module.on-prem.google_compute_instance.on_prem_in_a_box +tf taint 'module.vm-onprem.google_compute_instance.default["onprem-1"]' tf apply ``` @@ -89,7 +89,7 @@ google.internal { ```bash # connect to the onprem instance -gcloud compute ssh onprem +gcloud compute ssh onprem-1 # check that the BGP session works and the advertised routes are set sudo docker exec -it onprem_bird_1 ip route |grep bird @@ -101,6 +101,12 @@ sudo docker exec -it onprem_bird_1 ip route |grep bird # get a shell on the toolbox container sudo docker exec -it onprem_toolbox_1 sh +# test pinging the IP address of the test instance (check outputs for it) +ping 10.0.0.3 + +# note: if you are able to ping the IP but the DNS tests below do not work, +# refer to the sections above on configuring the DNS inbound fwd IP + # test forwarding from CoreDNS via the Cloud DNS inbound policy dig test-1.gcp.example.org +short 10.0.0.3