Hello ,

I have a PCFdev setup and when evr we deploy an application or do any administration of PCFdev where do we connect ,
Is it that all locally we do this or do we connect to PCF ,
Secondly if we are connecting to PCF why are we connecting
and if we are not connecting to PCF why do I need to have internet to push the applications, when I disable the internet we get error.
or we cannot even see the console.

Hi Praveen,

PCF Dev does not connect to a separate PCF or CF installation. PCF Dev can
be administered using the cf CLI (by following the instructions at boot) or
using Apps Manager (by opening a browser to https://local.pcfdev.io).

PCF Dev requires an internet connection to resolve *.local.pcfdev.io
addresses using public DNS. If you would like to run PCF Dev without an
internet connection, see here:
http://docs.pivotal.io/pcf-dev/work-offline.html

In the future, questions about PCF Dev can be asked at our Github issue
tracker: http://docs.pivotal.io/pcf-dev/work-offline.html

Thanks,
Stephen
PCF Dev PM

On Tue, Sep 20, 2016 at 11:41 AM, Praveen sadineni <sadinenip(a)gmail.com>
wrote:

Hello ,

I have a PCFdev setup and when evr we deploy an application or do any
administration of PCFdev where do we connect ,
Is it that all locally we do this or do we connect to PCF ,
Secondly if we are connecting to PCF why are we connecting
and if we are not connecting to PCF why do I need to have internet to push
the applications, when I disable the internet we get error.
or we cannot even see the console.

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).

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).

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).

Hello Daniel,

if that is the case and if it is going to public DNS how it is resolving to which VM's it has to be , for example I have used the same IP and other 2 members also used the same IP and if it is connecting to public which IP will be resolved to serve.

Hi Praveen,

It doesn't matter who looks up anything.local.pcfdev.io. The answer is
always the same address, which is always local: 192.168.11.11. It's a bit
like if the DNS record always returned 127.0.0.1 (localhost):
http://networkengineering.stackexchange.com/a/5830

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 8:35 PM, Praveen sadineni <sadinenip(a)gmail.com>
wrote:

Hello Daniel,

if that is the case and if it is going to public DNS how it is resolving
to which VM's it has to be , for example I have used the same IP and other
2 members also used the same IP and if it is connecting to public which IP
will be resolved to serve.

Hello Stephen,

I am using Windows 10 and I have opened a issue in Github.