The [Machines] section shows IP addresses in the DNS column:
[Machines]
ID STATE DNS INS-ID SERIES AZ
0 started 10.0.3.153 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-0 trusty
1 started 10.0.3.40 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-1 trusty
2 started 10.0.3.239 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-2 trusty
3 started 10.0.3.142 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-3 trusty
4 started 10.0.3.149 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-4 trusty
5 started 10.0.3.20 juju-1e7704dd-ddd5-4197-8bd5-9c9c7585a21d-machine-5 trusty
Maybe it should be ADDRESS instead?
Yeah, compare juju1 with juju2 (different machines, but same maas controller):
juju1: 1.0/nodes/ node-2fdcca2c- 39eb-11e5- ab72-2c59e54ace 74/ trusty arch=amd64 cpu-cores=4 mem=16384M availability- zone=dawn
[Machines]
ID STATE VERSION DNS INS-ID SERIES HARDWARE
0 started 1.25.5 omaha.scapestack /MAAS/api/
juju2 beta6: 1.0/nodes/ node-54a9d17c- f77f-11e5- ad3e-2c59e54ace 75/ xenial dawn
[Machines]
ID STATE DNS INS-ID SERIES AZ
0 started 10.96.10.1 /MAAS/api/
That IP is resolvable:
$ dig +short @10.96.0.10 -x 10.96.10.1
elkhart.scapestack.
$ dig +short @10.96.0.10 elkhart.scapestack
10.96.10.1