Bug#801362: /lib/x86_64-linux-gnu/libnss_dns.so.2: Host names ending in ".localhost" do not return the loopback address as specified by RFC6761.

[Aurelien Jarno]

control: severity -1 wishlist

On 2015-10-08 22:30, y.st. wrote:
> Package: libc6
> Version: 2.19-18+deb8u1
> 
> Dear Maintainer,
> 
> * What led up to the situation?
> 
> I was testing virtual hosts locally in Apache and set up a host that
> responds
> with a different site depending on the host name it recieves.
> 
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> 
> I tried loading  in the Web browser.
> 
>* What was the outcome of this action?
> 
> My machine quiried my ISP's name server and returned an advertizement
> page.
> 
>* What outcome did you expect instead?
> 
> My machine should have returned the loopback address without querying my
> ISP's
> name server, then loaded the website from my local machine as specified
> by
> RFC6761:
> 
> 
> 6.3.  Domain Name Reservation Considerations for "localhost."
> 
> The domain "localhost." and any names falling within
> ".localhost."
> are special in the following ways:
> 
> 3.  Name resolution APIs and libraries SHOULD recognize
> localhost
> names as special and SHOULD always return the IP
> loopback
> address
> for address queries and negative responses for all other
> query
> types.  Name resolution APIs SHOULD NOT send queries for
> localhost names to their configured caching DNS
> server(s).

This RFC is relatively new and almost nobody implemented it yet. I am
therefore downgrading this bug as a wishlist.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#801362: /lib/x86_64-linux-gnu/libnss_dns.so.2: Host names ending in ".localhost" do not return the loopback address as specified by RFC6761.

[y.st.]

Package: libc6
Version: 2.19-18+deb8u1

Dear Maintainer,

* What led up to the situation?

I was testing virtual hosts locally in Apache and set up a host that
responds
with a different site depending on the host name it recieves.

* What exactly did you do (or not do) that was effective (or
ineffective)?

I tried loading  in the Web browser.

   * What was the outcome of this action?

My machine quiried my ISP's name server and returned an advertizement
page.

   * What outcome did you expect instead?

My machine should have returned the loopback address without querying my
ISP's
name server, then loaded the website from my local machine as specified
by
RFC6761:


6.3.  Domain Name Reservation Considerations for "localhost."

The domain "localhost." and any names falling within
".localhost."
are special in the following ways:

3.  Name resolution APIs and libraries SHOULD recognize
localhost
names as special and SHOULD always return the IP
loopback
address
for address queries and negative responses for all other
query
types.  Name resolution APIs SHOULD NOT send queries for
localhost names to their configured caching DNS
server(s).



-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (500,
'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=eo.utf8, LC_CTYPE=eo.utf8 (charmap=ANSI_X3.4-1968)
(ignored: LC_ALL set to POSIX)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libc6:amd64 depends on:
ii  libgcc1  1:4.9.2-10

libc6:amd64 recommends no packages.

Versions of packages libc6:amd64 suggests:
ii  debconf [debconf-2.0]  1.5.56
pn  glibc-doc  
ii  locales2.19-18+deb8u1

-- debconf information:
  glibc/restart-failed:
  glibc/disable-screensaver:
  glibc/restart-services: