On 2015-04-04 10:02:22 +0100, Joe wrote:
On Fri, 3 Apr 2015 20:39:26 -0500
David Wright deb...@lionunicorn.co.uk wrote:
I think I/we ought to be using .local
http://tools.ietf.org/html/rfc6762
because this won't get onto the Internet.
Really? I've seen an Exchange Server refuse mail
On Tue, 7 Apr 2015 13:23:33 +0200
Vincent Lefevre vinc...@vinc17.net wrote:
On 2015-04-04 10:02:22 +0100, Joe wrote:
On Fri, 3 Apr 2015 20:39:26 -0500
David Wright deb...@lionunicorn.co.uk wrote:
I think I/we ought to be using .local
http://tools.ietf.org/html/rfc6762
because this
Brian wrote:
Every time I use d-i in expert mode I wonder what other people make of
it. I was puzzled by it the very first time and even now think it is
one of the most difficult fields to fill in because the background
knowledge needed isn't immediately as apparent as it is with language
or
On Fri, 3 Apr 2015 20:39:26 -0500
David Wright deb...@lionunicorn.co.uk wrote:
I think I/we ought to be using .local
http://tools.ietf.org/html/rfc6762
because this won't get onto the Internet.
Really? I've seen an Exchange Server refuse mail from a BT server
because the latter
Brian wrote:
Bob Proulx wrote:
The debian-installer will set things up right with an entry such as
this one.
127.0.1.1 foo.example.com foo
If 'Domain name' is blank you get '127.0.1.1 foo'.
Ah, yes, I had left that out. We had discussed that point in a
previous email. However I
On Fri 03 Apr 2015 at 14:29:49 -0600, Bob Proulx wrote:
Brian wrote:
Bob Proulx wrote:
The debian-installer will set things up right with an entry such as
this one.
127.0.1.1 foo.example.com foo
If 'Domain name' is blank you get '127.0.1.1 foo'.
Ah, yes, I had left that
Quoting Brian (a...@cityscape.co.uk):
On Fri 03 Apr 2015 at 14:29:49 -0600, Bob Proulx wrote:
Brian wrote:
Bob Proulx wrote:
The debian-installer will set things up right with an entry such as
this one.
127.0.1.1 foo.example.com foo
If 'Domain name' is blank you
Quoting David Wright (deb...@lionunicorn.co.uk):
I'm one of the many who use .home
https://tools.ietf.org/html/draft-cheshire-homenet-dot-home-00
and this paper points out that there's an awful lot of leakage onto
the Internet.
I think I/we ought to be using .local
On Thu 02 Apr 2015 at 16:47:56 -0600, Bob Proulx wrote:
Alex Mestiashvili wrote:
and as far as I see it simply asks the DNS about the hostname using
getaddrinfo.
But, with stock nsswitch.conf, it issues uname(2) syscall first, goes
to /etc/hosts second, and if it encounters FQDN
Alex Mestiashvili wrote:
and as far as I see it simply asks the DNS about the hostname using
getaddrinfo.
But, with stock nsswitch.conf, it issues uname(2) syscall first, goes
to /etc/hosts second, and if it encounters FQDN hostname - it all ends
here.
If /etc/hosts contain only
Hi al,
WHen issuing 'hostname --fqdn', I'm supposed to get the FQDN.
Anyway when trying some different combinations, involving /etc/hostname,
/etc/domainname, /etc/hosts, /etc/resolv.conf, I cannot figure out where
the FQDN is looked up AND with what precedence.
Would you know the mechanism
On 04/02/2015 02:10 PM, Mihamina Rakotomandimby wrote:
Hi al,
WHen issuing 'hostname --fqdn', I'm supposed to get the FQDN.
Anyway when trying some different combinations, involving
/etc/hostname, /etc/domainname, /etc/hosts, /etc/resolv.conf, I cannot
figure out where the FQDN is looked up
and as far as I see it simply asks the DNS about the hostname using
getaddrinfo.
But, with stock nsswitch.conf, it issues uname(2) syscall first, goes
to /etc/hosts second, and if it encounters FQDN hostname - it all ends
here.
If /etc/hosts contain only bare hostname - it'd return a
Hi.
On Thu, 02 Apr 2015 14:54:19 +0200
Alex Mestiashvili a...@biotec.tu-dresden.de wrote:
the mechanism is described here:
http://sources.debian.net/src/hostname/3.15/hostname.c/
and as far as I see it simply asks the DNS about the hostname using
getaddrinfo.
But, with stock
14 matches
Mail list logo
