Hi Daniel,

I've prioritized a story to investigate your StackExchange issue. We'll
update the documentation with any findings.

Praveen, are you also running OS X? Can you open a PCF Dev Github issue
describing how the work offline doc fails for you?

Thanks,
Stephen

On Tue, Sep 20, 2016 at 3:12 PM, Daniel Jones <
daniel.jones(a)engineerbetter.com> wrote:

Hi Praveen,

The name records for *.local.pcfdev.io always refer back to the same
(local) IP: 192.168.11.11. So you make a call out to the public internet to
resolve the DNS record, but then requests are only send to the VM running
locally.

I've had issues trying to get DNSMasq to work as documented on my Mac, and
I haven't had time to get to the bottom of it yet: http://apple.
stackexchange.com/questions/251678/dns-resolution-fails-
for-ping-and-curl-but-not-dig

Regards,
Daniel Jones - CTO
+44 (0)79 8000 9153
@DanielJonesEB <https://twitter.com/DanielJonesEB>
*EngineerBetter* Ltd <http://www.engineerbetter.com> - UK Cloud Foundry
Specialists

On Tue, Sep 20, 2016 at 7:33 PM, Praveen sadineni <sadinenip(a)gmail.com>
wrote:

How is it resolving the DNS when we have PCF dev locally?

When we connect to https://local.pcfdev.io it basically redirects to
console.local.pcfdev.io and again redirecting to uaa.local.pcfdev.io ,
which means it is connecting some how some where , where does this user
authentication happen.

We have tried the setup to make use locally and it is not sucessful.(
http://docs.pivotal.io/pcf-dev/work-offline.html).