Why does *.localhost resolve to 127.0.0.1 and ::1?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
3
down vote

favorite












I discovered by chance (trying to access a proxied service in a Docker container on a Vagrant box using servicename.docker.localhost from the host) that any hostname ending in ".localhost" resolves to 127.0.0.1 or ::1 on my machine:



$ ping -4 -c1 -n foo.localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.147 ms

--- localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.147/0.147/0.147/0.000 ms
$ ping -6 -c1 -n foo.localhost
PING foo.localhost(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.072 ms

--- foo.localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.072/0.072/0.072/0.000 ms


However, there is no DNS entry for this:



$ nslookup -type=AAAA foo.localhost
Server: 192.168.2.82
Address: 192.168.2.82#53

** server can't find foo.localhost: NXDOMAIN
$ nslookup -type=A foo.localhost
Server: 192.168.2.82
Address: 192.168.2.82#53

** server can't find foo.localhost: NXDOMAIN


/etc/hosts doesn't look particularly relevant:



127.0.0.1 my-machine-name.my-work-domain my-machine-name localhost.localdomain localhost
::1 localhost.localdomain localhost


Neither does /etc/resolv.conf:



domain my-work-domain
search my-work-domain
nameserver 192.[…]
nameserver 192.[…]


Why does *.localhost magically resolve?



This is similar but possibly distinct from this question.



$ getent hosts
127.0.0.1 my-machine-name.my-work-domain my-machine-name localhost.localdomain localhost
127.0.0.1 localhost.localdomain localhost
$ getent hosts foo.localhost
::1 localhost



arch-linux dns




share|improve this question





















  • What does getent say?
    – Ignacio Vazquez-Abrams
    May 28 at 0:16










  • Are you using systemd? It has a last resort resolver that (if none other nameserver resolved it before) resolves localhost to ::1.
    – Isaac
    May 28 at 9:04










  • @Isaac I think you can write that as an answer. From the page you linked to: "systemd-resolved synthesizes DNS resource records (RRs) for the following cases: [...] any hostname ending in ".localhost" or ".localhost.localdomain") are resolved to the IP addresses 127.0.0.1 and ::1"
    – Johan Myréen
    May 28 at 15:47










  • Also just FYI, before /etc/resolv.conf and /etc/hosts there is /etc/nsswitch.conf which controls what sources the libc resolver uses, and in what order. grep '^hosts:' /etc/nsswitch.conf.
    – Patrick
    May 28 at 19:54














up vote
3
down vote

favorite












I discovered by chance (trying to access a proxied service in a Docker container on a Vagrant box using servicename.docker.localhost from the host) that any hostname ending in ".localhost" resolves to 127.0.0.1 or ::1 on my machine:



$ ping -4 -c1 -n foo.localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.147 ms

--- localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.147/0.147/0.147/0.000 ms
$ ping -6 -c1 -n foo.localhost
PING foo.localhost(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.072 ms

--- foo.localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.072/0.072/0.072/0.000 ms


However, there is no DNS entry for this:



$ nslookup -type=AAAA foo.localhost
Server: 192.168.2.82
Address: 192.168.2.82#53

** server can't find foo.localhost: NXDOMAIN
$ nslookup -type=A foo.localhost
Server: 192.168.2.82
Address: 192.168.2.82#53

** server can't find foo.localhost: NXDOMAIN


/etc/hosts doesn't look particularly relevant:



127.0.0.1 my-machine-name.my-work-domain my-machine-name localhost.localdomain localhost
::1 localhost.localdomain localhost


Neither does /etc/resolv.conf:



domain my-work-domain
search my-work-domain
nameserver 192.[…]
nameserver 192.[…]


Why does *.localhost magically resolve?



This is similar but possibly distinct from this question.



$ getent hosts
127.0.0.1 my-machine-name.my-work-domain my-machine-name localhost.localdomain localhost
127.0.0.1 localhost.localdomain localhost
$ getent hosts foo.localhost
::1 localhost



arch-linux dns




share|improve this question





















  • What does getent say?
    – Ignacio Vazquez-Abrams
    May 28 at 0:16










  • Are you using systemd? It has a last resort resolver that (if none other nameserver resolved it before) resolves localhost to ::1.
    – Isaac
    May 28 at 9:04










  • @Isaac I think you can write that as an answer. From the page you linked to: "systemd-resolved synthesizes DNS resource records (RRs) for the following cases: [...] any hostname ending in ".localhost" or ".localhost.localdomain") are resolved to the IP addresses 127.0.0.1 and ::1"
    – Johan Myréen
    May 28 at 15:47










  • Also just FYI, before /etc/resolv.conf and /etc/hosts there is /etc/nsswitch.conf which controls what sources the libc resolver uses, and in what order. grep '^hosts:' /etc/nsswitch.conf.
    – Patrick
    May 28 at 19:54












up vote
3
down vote

favorite









up vote
3
down vote

favorite











I discovered by chance (trying to access a proxied service in a Docker container on a Vagrant box using servicename.docker.localhost from the host) that any hostname ending in ".localhost" resolves to 127.0.0.1 or ::1 on my machine:



$ ping -4 -c1 -n foo.localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.147 ms

--- localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.147/0.147/0.147/0.000 ms
$ ping -6 -c1 -n foo.localhost
PING foo.localhost(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.072 ms

--- foo.localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.072/0.072/0.072/0.000 ms


However, there is no DNS entry for this:



$ nslookup -type=AAAA foo.localhost
Server: 192.168.2.82
Address: 192.168.2.82#53

** server can't find foo.localhost: NXDOMAIN
$ nslookup -type=A foo.localhost
Server: 192.168.2.82
Address: 192.168.2.82#53

** server can't find foo.localhost: NXDOMAIN


/etc/hosts doesn't look particularly relevant:



127.0.0.1 my-machine-name.my-work-domain my-machine-name localhost.localdomain localhost
::1 localhost.localdomain localhost


Neither does /etc/resolv.conf:



domain my-work-domain
search my-work-domain
nameserver 192.[…]
nameserver 192.[…]


Why does *.localhost magically resolve?



This is similar but possibly distinct from this question.



$ getent hosts
127.0.0.1 my-machine-name.my-work-domain my-machine-name localhost.localdomain localhost
127.0.0.1 localhost.localdomain localhost
$ getent hosts foo.localhost
::1 localhost



arch-linux dns




share|improve this question













I discovered by chance (trying to access a proxied service in a Docker container on a Vagrant box using servicename.docker.localhost from the host) that any hostname ending in ".localhost" resolves to 127.0.0.1 or ::1 on my machine:



$ ping -4 -c1 -n foo.localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.147 ms

--- localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.147/0.147/0.147/0.000 ms
$ ping -6 -c1 -n foo.localhost
PING foo.localhost(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.072 ms

--- foo.localhost ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.072/0.072/0.072/0.000 ms


However, there is no DNS entry for this:



$ nslookup -type=AAAA foo.localhost
Server: 192.168.2.82
Address: 192.168.2.82#53

** server can't find foo.localhost: NXDOMAIN
$ nslookup -type=A foo.localhost
Server: 192.168.2.82
Address: 192.168.2.82#53

** server can't find foo.localhost: NXDOMAIN


/etc/hosts doesn't look particularly relevant:



127.0.0.1 my-machine-name.my-work-domain my-machine-name localhost.localdomain localhost
::1 localhost.localdomain localhost


Neither does /etc/resolv.conf:



domain my-work-domain
search my-work-domain
nameserver 192.[…]
nameserver 192.[…]


Why does *.localhost magically resolve?



This is similar but possibly distinct from this question.



$ getent hosts
127.0.0.1 my-machine-name.my-work-domain my-machine-name localhost.localdomain localhost
127.0.0.1 localhost.localdomain localhost
$ getent hosts foo.localhost
::1 localhost




arch-linux dns





share|improve this question












share|improve this question




share|improve this question








edited May 28 at 3:39
























asked May 27 at 23:34









l0b0

26k17104226




26k17104226











  • What does getent say?
    – Ignacio Vazquez-Abrams
    May 28 at 0:16










  • Are you using systemd? It has a last resort resolver that (if none other nameserver resolved it before) resolves localhost to ::1.
    – Isaac
    May 28 at 9:04










  • @Isaac I think you can write that as an answer. From the page you linked to: "systemd-resolved synthesizes DNS resource records (RRs) for the following cases: [...] any hostname ending in ".localhost" or ".localhost.localdomain") are resolved to the IP addresses 127.0.0.1 and ::1"
    – Johan Myréen
    May 28 at 15:47










  • Also just FYI, before /etc/resolv.conf and /etc/hosts there is /etc/nsswitch.conf which controls what sources the libc resolver uses, and in what order. grep '^hosts:' /etc/nsswitch.conf.
    – Patrick
    May 28 at 19:54
















  • What does getent say?
    – Ignacio Vazquez-Abrams
    May 28 at 0:16










  • Are you using systemd? It has a last resort resolver that (if none other nameserver resolved it before) resolves localhost to ::1.
    – Isaac
    May 28 at 9:04










  • @Isaac I think you can write that as an answer. From the page you linked to: "systemd-resolved synthesizes DNS resource records (RRs) for the following cases: [...] any hostname ending in ".localhost" or ".localhost.localdomain") are resolved to the IP addresses 127.0.0.1 and ::1"
    – Johan Myréen
    May 28 at 15:47










  • Also just FYI, before /etc/resolv.conf and /etc/hosts there is /etc/nsswitch.conf which controls what sources the libc resolver uses, and in what order. grep '^hosts:' /etc/nsswitch.conf.
    – Patrick
    May 28 at 19:54















What does getent say?
– Ignacio Vazquez-Abrams
May 28 at 0:16




What does getent say?
– Ignacio Vazquez-Abrams
May 28 at 0:16












Are you using systemd? It has a last resort resolver that (if none other nameserver resolved it before) resolves localhost to ::1.
– Isaac
May 28 at 9:04




Are you using systemd? It has a last resort resolver that (if none other nameserver resolved it before) resolves localhost to ::1.
– Isaac
May 28 at 9:04












@Isaac I think you can write that as an answer. From the page you linked to: "systemd-resolved synthesizes DNS resource records (RRs) for the following cases: [...] any hostname ending in ".localhost" or ".localhost.localdomain") are resolved to the IP addresses 127.0.0.1 and ::1"
– Johan Myréen
May 28 at 15:47




@Isaac I think you can write that as an answer. From the page you linked to: "systemd-resolved synthesizes DNS resource records (RRs) for the following cases: [...] any hostname ending in ".localhost" or ".localhost.localdomain") are resolved to the IP addresses 127.0.0.1 and ::1"
– Johan Myréen
May 28 at 15:47












Also just FYI, before /etc/resolv.conf and /etc/hosts there is /etc/nsswitch.conf which controls what sources the libc resolver uses, and in what order. grep '^hosts:' /etc/nsswitch.conf.
– Patrick
May 28 at 19:54




Also just FYI, before /etc/resolv.conf and /etc/hosts there is /etc/nsswitch.conf which controls what sources the libc resolver uses, and in what order. grep '^hosts:' /etc/nsswitch.conf.
– Patrick
May 28 at 19:54










1 Answer
1






active

oldest

votes

















up vote
3
down vote



accepted










This is caused by the myhostname NSS module which defines the hostname and any name ending in .localhost as 127.0.0.1 in ipv4 and ::1 in ipv6.



https://www.freedesktop.org/software/systemd/man/nss-myhostname.html






share|improve this answer





















  • nss-systemd could theoretically do something similar but not only is Arch Linux not configured like this by default nor is systemd.
    – jdwolf
    May 28 at 20:49










  • You nailed it - /etc/nsswitch.conf enables myhostname.
    – l0b0
    May 28 at 20:58











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446371%2fwhy-does-localhost-resolve-to-127-0-0-1-and-1%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
3
down vote



accepted










This is caused by the myhostname NSS module which defines the hostname and any name ending in .localhost as 127.0.0.1 in ipv4 and ::1 in ipv6.



https://www.freedesktop.org/software/systemd/man/nss-myhostname.html






share|improve this answer





















  • nss-systemd could theoretically do something similar but not only is Arch Linux not configured like this by default nor is systemd.
    – jdwolf
    May 28 at 20:49










  • You nailed it - /etc/nsswitch.conf enables myhostname.
    – l0b0
    May 28 at 20:58















up vote
3
down vote



accepted










This is caused by the myhostname NSS module which defines the hostname and any name ending in .localhost as 127.0.0.1 in ipv4 and ::1 in ipv6.



https://www.freedesktop.org/software/systemd/man/nss-myhostname.html






share|improve this answer





















  • nss-systemd could theoretically do something similar but not only is Arch Linux not configured like this by default nor is systemd.
    – jdwolf
    May 28 at 20:49










  • You nailed it - /etc/nsswitch.conf enables myhostname.
    – l0b0
    May 28 at 20:58













up vote
3
down vote



accepted







up vote
3
down vote



accepted






This is caused by the myhostname NSS module which defines the hostname and any name ending in .localhost as 127.0.0.1 in ipv4 and ::1 in ipv6.



https://www.freedesktop.org/software/systemd/man/nss-myhostname.html






share|improve this answer













This is caused by the myhostname NSS module which defines the hostname and any name ending in .localhost as 127.0.0.1 in ipv4 and ::1 in ipv6.



https://www.freedesktop.org/software/systemd/man/nss-myhostname.html







share|improve this answer













share|improve this answer



share|improve this answer











answered May 28 at 20:48









jdwolf

2,362116




2,362116











  • nss-systemd could theoretically do something similar but not only is Arch Linux not configured like this by default nor is systemd.
    – jdwolf
    May 28 at 20:49










  • You nailed it - /etc/nsswitch.conf enables myhostname.
    – l0b0
    May 28 at 20:58

















  • nss-systemd could theoretically do something similar but not only is Arch Linux not configured like this by default nor is systemd.
    – jdwolf
    May 28 at 20:49










  • You nailed it - /etc/nsswitch.conf enables myhostname.
    – l0b0
    May 28 at 20:58
















nss-systemd could theoretically do something similar but not only is Arch Linux not configured like this by default nor is systemd.
– jdwolf
May 28 at 20:49




nss-systemd could theoretically do something similar but not only is Arch Linux not configured like this by default nor is systemd.
– jdwolf
May 28 at 20:49












You nailed it - /etc/nsswitch.conf enables myhostname.
– l0b0
May 28 at 20:58





You nailed it - /etc/nsswitch.conf enables myhostname.
– l0b0
May 28 at 20:58













 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446371%2fwhy-does-localhost-resolve-to-127-0-0-1-and-1%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more