Add pointer in case the service cannot be resolved (#4102)

* Add pointer in case the service cannot be resolved

The service in the tutorial could not be resolved. It is not immediately apparent why this is the case (VPN, FritzBox DNS Server, etc). The tips in the comments solved the problem for me.

* Change indentation of question

* Swap links for solution steps

* Update docs/getting-started/first-service.md

Better working of the problem.

Co-authored-by: Julian Friedman <julz.friedman@uk.ibm.com>

* PR changes

* Update docs/getting-started/first-service.md

Co-authored-by: Julian Friedman <julz.friedman@uk.ibm.com>
Co-authored-by: Ashleigh Brennan <abrennan@redhat.com>
This commit is contained in:
Steve Boardwell 2021-09-01 14:43:33 +02:00 committed by GitHub
parent fc937b90ad
commit 5f22aa69df
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 0 deletions

View File

@ -78,4 +78,20 @@ curl http://hello.default.127.0.0.1.nip.io
Hello World!
```
??? question "Are you seeing `curl: (6) Could not resolve host: hello.default.127.0.0.1.nip.io`?"
In some cases your DNS server may be set up not to resolve `*.nip.io` addresses. If you encounter this problem, it can be fixed by using a different nameserver to resolve these addresses.
The exact steps will differ according to your distribution. For example, with Ubuntu derived systems which use `systemd-resolved`, you can add the following entry to the `/etc/systemd/resolved.conf`:
```ini
[Resolve]
DNS=8.8.8.8
Domains=~nip.io.
```
Then simply restart the service with `sudo service systemd-resolved restart`.
For MacOS users, you can add the DNS and domain using the network settings as explained [here](https://support.apple.com/en-gb/guide/mac-help/mh14127/mac).
Congratulations :tada:, you've just created your first Knative Service. Up next, Autoscaling!