Formerly Netinfo as I recall, now the local component of Open Directory /
directory services. Database files are in /var/db/dslocal and are binary
plists, except for an sqlite3 index file and a couple of files associated with
it. _Looking_ at those directly (I wouldn’t modify anything directly
On Sunday January 04 2015 20:18:26 Brandon Allbery wrote:
> On Sun, Jan 4, 2015 at 8:14 PM, René J.V. wrote:
>
> > #> head /etc/hosts
> > ##
> > # Host Database
> > #
> > # localhost is used to configure the loopback interface
> > # when the system is booting. Do not change this entry.
> > ##
>
On Sun, Jan 4, 2015 at 8:14 PM, René J.V. wrote:
> #> head /etc/hosts
> ##
> # Host Database
> #
> # localhost is used to configure the loopback interface
> # when the system is booting. Do not change this entry.
> ##
>
> 127.0.0.1 localhost Portia
> 255.255.255.255 broadcasthost
> # RJVB
On Sunday January 04 2015 16:51:42 Justin C. Walker wrote:
> > (It is *not*, however, in /Hosts.)
>
> Do you mean that "localhost" is not mentioned in /etc/hosts? I can't verify
> that one way or another since my 10.10 system is an upgrade from several
> versions back.
My 10.9.5 is an upgrade
On Sun, Jan 4, 2015 at 7:51 PM, Justin C. Walker wrote:
> Do you mean that "localhost" is not mentioned in /etc/hosts? I can't
> verify that one way or another since my 10.10 system is an upgrade from
> several versions back.
>
No, I mean it is not listed in DirectoryServices under the Hosts ke
On Jan 4, 2015, at 16:31 , Brandon Allbery wrote:
> On Sun, Jan 4, 2015 at 7:27 PM, Brandon Allbery wrote:
>
>> On Sun, Jan 4, 2015 at 7:08 PM, Justin C. Walker wrote:
>>
>>> To answer another question from earlier in the thread, I believe the
>>> "database" used by Mac OS X during the early
On Jan 4, 2015, at 16:27 , Brandon Allbery wrote:
> On Sun, Jan 4, 2015 at 7:08 PM, Justin C. Walker wrote:
>
>> To answer another question from earlier in the thread, I believe the
>> "database" used by Mac OS X during the early years was a hold-over from
>> NeXT days (netinfo?). I think it w
On Sun, Jan 4, 2015 at 7:27 PM, Brandon Allbery wrote:
> On Sun, Jan 4, 2015 at 7:08 PM, Justin C. Walker wrote:
>
>> To answer another question from earlier in the thread, I believe the
>> "database" used by Mac OS X during the early years was a hold-over from
>> NeXT days (netinfo?). I think
On Sun, Jan 4, 2015 at 7:08 PM, Justin C. Walker wrote:
> To answer another question from earlier in the thread, I believe the
> "database" used by Mac OS X during the early years was a hold-over from
> NeXT days (netinfo?). I think it was essentially gone by the time 10.6 was
> released.
>
Inc
On Jan 4, 2015, at 13:23 , René J.V. Bertin wrote:
> On Sunday January 04 2015 13:10:30 Justin C. Walker wrote:
>
>>> I have no trouble ssh-ing to localhost on my system, but Safari always
>>> responds "Can't connect to the Server."
>>
>> FWIW, i get this on my 10.6.8 system, which is more or
On Sun, Jan 4, 2015 at 4:23 PM, René J.V. wrote:
> TWO IPv6 addresses? Could you paste the relevant lines here?
>
Looks like there's an link-local address space reference in there as well
as ::1, presumably because the loopback adapter does not implement IPv6
link-local autoconfig (why, indeed,
On Sunday January 04 2015 13:10:30 Justin C. Walker wrote:
> > I have no trouble ssh-ing to localhost on my system, but Safari always
> > responds "Can't connect to the Server."
>
> FWIW, i get this on my 10.6.8 system, which is more or less "stock".
>
> Also, 'localhost' is defined in my /etc
To add to the chatter:
On Jan 3, 2015, at 13:41 , William H. Magill wrote:
> Did Apple change something in Yosemite/Safari so that "localhost" is no
> longer an accessible DNS address for Safari?
>
> I have no trouble ssh-ing to localhost on my system, but Safari always
> responds "Can't conn
On Sun, Jan 4, 2015 at 1:14 PM, René J.V. wrote:
> Not the server running on my modem/router (192.168.1.1) in any case. But
> it could be that router just forwards requests to the ISP's DNS servers if
> they don't match the entries in the MAC/hostname table.
It does; it's not a real nameserver,
On Sunday January 04 2015 12:28:50 Brandon Allbery wrote:
> not serve it to you, whereas a local nameserver usually would. (Roughly the
> same rule as for the RFC1918 private address ranges.)
Not the server running on my modem/router (192.168.1.1) in any case. But it
could be that router just fo
On Sun, Jan 4, 2015 at 12:23 PM, René J.V. wrote:
> And when I out-comment the localhost definition from /etc/hosts, I can no
> longer connect to that hostname.
That's because, while a nameserver often comes with a zone definition
providing a localhost definition, publishing it is a no-no. So 8
On Sunday January 04 2015 10:46:53 Brandon Allbery wrote:
> It'll be fine once commodity Internet and commodity routers/access points
> (aside from Apple's!) includes IPv6 connectivity. Currently, you'll find
> that getting IPv6 upstream is nearly impossible in many places / with many
> providers;
On Sun, Jan 4, 2015 at 11:49 AM, Michael Crawford
wrote:
> DNS is a protocol, not an API. To the extent that hosts is used, it's
> because developer of the software that implements the protocol chooses
> to use it.
>
That would be why I mentioned BSD API (used by most command line utilities)
an
DNS is a protocol, not an API. To the extent that hosts is used, it's
because developer of the software that implements the protocol chooses
to use it.
It's a PITA if it's not used - I quite commonly set up small networks
in my own office, with static IPs hardwired into my hosts files.
Michael Da
On Sun, Jan 4, 2015 at 11:20 AM, William H. Magill wrote:
> > BIND9 at least comes with a local zone definition that includes
> "localhost." as a name, with the usual mapping. That said, people *usually*
> get it from /etc/hosts... *but* OS X is a little weird in how/when it uses
> the hosts file
> On Jan 4, 2015, at 10:46 AM, Brandon Allbery wrote:
>
> On Sun, Jan 4, 2015 at 10:34 AM, René J.V. wrote:
> On Sunday January 04 2015 09:05:42 Brandon Allbery wrote:
>
> >From the standpoint of DNS, "localhost" is fully qualified: it is not the
> >short form of a name that is meaningful only
On Sun, Jan 4, 2015 at 10:34 AM, René J.V. wrote:
> On Sunday January 04 2015 09:05:42 Brandon Allbery wrote:
>
> >From the standpoint of DNS, "localhost" is fully qualified: it is not the
> >short form of a name that is meaningful only in the context of a
> particular
> >domain.
>
> AFAIK you ne
On Sun, Jan 4, 2015 at 2:06 AM, William H. Magill wrote:
> It also appears that the function of the ServerName directive has changed.
> The current Apache manual
> http://httpd.apache.org/docs/2.2/mod/core.html#servername
>
>
> describes its syntax as requiring a FQDN -- which neither Localhost n
On Jan 4, 2015, at 1:06 AM, William H. Magill wrote:
> What triggered my query was the fact that various "how to" pages describe
> using "localhost" as a mechanic for testing certain web based services --
> which did not work!
> https://trac.macports.org/wiki/howto/Apache2
> I'm guessing that t
HTTP 1.0 used only the IP address; if you wanted a single server to
serve multiple domains, it needed to have multiple IP addresses.
HTTP 1.1 permits the use of the hostname, and a single IP that
multiple hosts all share.
However, in general it should work to leave off the hostname. What
you'd g
On Jan 3, 2015, at 3:41 PM, William H. Magill wrote:
>
>> Did Apple change something in Yosemite/Safari so that "localhost" is no
>> longer an accessible DNS address for Safari?
>>
>> I have no trouble ssh-ing to localhost on my system, but Safari always
>> responds "Can't connect to the Serve
On Saturday January 03 2015 18:45:15 Ryan Schmidt wrote:
> I experience the problem on Yosemite that "localhost" will randomly switch
> between accessing the IPv4 address of my server (which works) and the IPv6
> address of my server (which apparently isn't working). I've had to start
> using "
On Sat, 3 Jan 2015, Ryan Schmidt wrote:
> I experience the problem on Yosemite that "localhost" will randomly
> switch between accessing the IPv4 address of my server (which works) and
> the IPv6 address of my server (which apparently isn't working). I've had
> to start using "127.0.0.1" instea
You might try
http://127.0.0.1/
and
http://[::1]/
(IPv4 and IPv6 addresses for localhost - use https and a port number if
required) If neither of those works either, it’s probably not the hostname
lookup (which is not necessarily just DNS, depending on how you’re configured).
Safari should
On Jan 3, 2015, at 3:41 PM, William H. Magill wrote:
> Did Apple change something in Yosemite/Safari so that "localhost" is no
> longer an accessible DNS address for Safari?
>
> I have no trouble ssh-ing to localhost on my system, but Safari always
> responds "Can't connect to the Server."
>
Did Apple change something in Yosemite/Safari so that "localhost" is no longer
an accessible DNS address for Safari?
I have no trouble ssh-ing to localhost on my system, but Safari always responds
"Can't connect to the Server."
Note that at one time I was using Apple's Apache via OSX Server, b
31 matches
Mail list logo
