CF DEV START: Request error: Get https://api.dev.cfdev.sh/v2/info: dial tcp: lookup api.dev.cfdev.sh: no such host

[thlcodes]

CF DEV START: Request error: Get https://api.dev.cfdev.sh/v2/info: dial tcp: lookup api.dev.cfdev.sh: no such host

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/170970330

The labels on this github issue will be updated when the story is started.

[aemengo]

Looks like a DNS issue: we’re seeing no such host. The domain api.dev.cfdev.sh can’t be resolved. Is your MacBook connected to the internet to make the resolution?

What does dig api.dev.cfdev.sh yield?

[thlcodes]

Yep, all devices are connected to the internet. Even my phone (on mobile data) cannot resolve the address.

$ dig api.dev.cfdev.sh

; <<>> DiG 9.10.6 <<>> api.dev.cfdev.sh
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46131
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;api.dev.cfdev.sh.              IN      A

;; Query time: 80 msec
;; SERVER: 192.168.52.1#53(192.168.52.1)
;; WHEN: Wed Jan 29 12:04:13 CET 2020
;; MSG SIZE  rcvd: 45

But, isn't CF DEV supposed to host the API? Via HTTPS with self-signed certificates? To me it looks more like the api cannot be served or the name resolving does not work.

[aemengo]

Thanks for the response. It definitely appears like address cannot be resolved on your machine. I'm afraid that getting that to resolve is outside scope of this repository. Maybe a quick fix might be to temporarily change your DNS address to 8.8.8.8 and then see if the dig command works.

isn't CF DEV supposed to host the API?

Yes, it is supposed to host the API. Nothing that you've posted so far indicates that the api didn't come up successfully on your machine, only you cannot reach it via the domain name: api.dev.cfdev.sh. This is a publicly registered domain name, so you'll need internet access to resolve it. You should have the following answer (10.144.0.34):

;; ANSWER SECTION:
api.dev.cfdev.sh.	60	IN	A	10.144.0.34

[kubiani]

Was experiencing the same issue. Tracked it down to rebinding protection on my pfSense box as the culprit. If you're using any custom router solution (ddwrt, openwrt, tomato, etc) it's probably the same deal. You'll need to disable rebinding protection or find out how to add exceptions for your setup.

For pfSense with the DNS Resolver enabled, add a line to the custom options to create an exception:

private-domain: "cfdev.sh"

Note: This is an unbound dns config option so this should work anywhere unbound is used as the backing dns resolver; you just need to add/inject it into unbound.conf. The private-domain option includes all subdomains as well so I used cfdev.sh but you may be able to get away with dev.cfdev.sh. However, there are multiple subdomains under the dev portion (api, login, uaa) that need to resolve so if you just use api.dev.cfdev.sh it'll fail somewhere else later on.