# Resolve pi.hole/localhost as FQDN

**URL:** <https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136>\
**Category:** Help\
**Tags:** docker\
**Created:** [September 24, 2022, 12:58pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136 "2022-09-24T12:58:57Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![sscheib](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/df705f/32.png) [@sscheib](https://discourse.pi-hole.net/u/sscheib)\
**Post date:** [September 24, 2022, 12:58pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/1 "2022-09-24T12:58:57Z")

</div>

## Expected Behaviour:

I'd like to have the pihole instance to report with it's fully qualified domain name in the API/WebUI, rather than pi.hole or localhost.  
I am running the official container image:

- **Docker Tag** [2022.09.4](https://github.com/pi-hole/docker-pi-hole/releases/2022.09.4)
- **Pi-hole** [v5.12.2](https://github.com/pi-hole/pi-hole/releases/v5.12.2)
- **FTL** [v5.18.1](https://github.com/pi-hole/FTL/releases/v5.18.1)
- **Web Interface** [v5.15.1](https://github.com/pi-hole/AdminLTE/releases/v5.15.1)

The container is running with podman version 4.1.1 on a RHEL 8.6. Following is the podman/docker-compose file that is being used:

```auto
version: "3"

services:
  pihole.example.com:
    container_name: 'pihole.example.com'
    hostname: 'pihole.example.com'
    image: 'pihole/pihole:latest'
    logging:
      driver: 'journald'
    ports:
      - "172.31.4.102:53:53/tcp"
      - "172.31.4.102:53:53/udp"
      - "127.0.0.1:8080:80/tcp"
    environment:
      TZ: 'Europe/Berlin'
      FTLCONF_LOCAL_IPV4: '172.31.4.102'
      CUSTOM_CACHE_SIZE: '10000'
      FLTCONF_PIHOLE_PTR: 'HOSTNAMEFQDN'
    volumes:
      - '/container/pihole.example.com/pihole:/etc/pihole:Z'
      - '/container/pihole.example.com/dnsmasq.d:/etc/dnsmasq.d:Z'
      - '/container/pihole.example.com/logs:/var/log:Z'
    restart: 'unless-stopped'
    cap_add:
      - CAP_AUDIT_WRITE
      - CAP_SYS_NICE
      - CAP_CHOWN
    deploy:
      resources:
        limits:
          memory: 2048M
        reservations:
          memory: 2048M

```

Is there a way to change the behavior so pihole will show itself with it's FQDN?

## Actual Behaviour:

In the WebUI/API pihole is shown as either pi.hole or localhost, instead of pihole.example.com. All other hosts are properly shown with FQDN.

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [September 24, 2022, 2:26pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/2 "2022-09-24T14:26:01Z")

</div>

> [@sscheib](#):
>
> I'd like to have the pihole instance to report with it's fully qualified domain name in the API/WebUI, rather than pi.hole or localhost.

> **[Configuration - Pi-hole documentation](https://docs.pi-hole.net/ftldns/configfile/#pihole_ptr)**

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [September 24, 2022, 3:16pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/3 "2022-09-24T15:16:10Z")

</div>

And since you are running a dockered Pi-hole, configure **`FTLCONF_PIHOLE_PTR`** as an [Advanced Environment Variable](https://github.com/pi-hole/docker-pi-hole#advanced-variables) to apply **jfb**'s suggestion:to a Docker container, see specifically:

> | Variable | Default | Value | Description |
> | --- | --- | --- | --- |
> | FTLCONF\_[SETTING] | unset | As per documentation | Customize pihole-FTL.conf with settings described in the FTLDNS Configuration page. For example, to customize LOCAL\_IPV4, ensure you have the FTLCONF\_LOCAL\_IPV4 environment variable set. |

---

<div class="post-metadata">

**Author:** ![sscheib](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/df705f/32.png) [@sscheib](https://discourse.pi-hole.net/u/sscheib)\
**Post date:** [September 25, 2022, 1:53am UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/4 "2022-09-25T01:53:30Z")

</div>

That's exactly what I applied already (please see the above codeblock for the `FLTCONF_PIHOLE_PTR` environment variable). I further also provided the domain (as suggested in the documentation) via:

```auto
[root@container pihole]# cat /container/pihole.example.com/dnsmasq.d/99-hostname.conf 
domain=example.com

```

Sorry, I forgot to mention that in the first post.

I am mounting `/container/pihole.example.com/dnsmasq.d` to `/etc/dnsmasq.d` and thus would expect that pihole would pick up that change actually.  
Nothing in the startup logs indicate however, if those environment variables are actually taken into consideration.  
I would have expected that they'll end up in `/container/pihole.example.com/pihole/pihole-FTL.conf`, but they don't:

```auto
[root@container pihole]# cat /container/pihole.example.com/pihole/pihole-FTL.conf 
REPLY_ADDR4=172.31.3.47
LOCAL_IPV4=172.31.3.47
RATE_LIMIT=1000/60

```

Please note, that I have also mounted `/container/pihole.example.com/pihole` to `/etc/pihole`.  
I tried adding `PIHOLE_PTR` directly to `/container/pihole.example.com/pihole/pihole-FTL.conf`, but that didn't work out either.

I have created a debug log, maybe that helps in pinning down the issue. Probably it's something configuration-wise on my end that doesn't work out.

Thanks for your help guys!

Debug log: [https://tricorder.pi-hole.net/23R5Hf1x/](https://tricorder.pi-hole.net/23R5Hf1x/)

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [September 25, 2022, 3:04am UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/5 "2022-09-25T03:04:41Z")

</div>

> [@sscheib](#):
>
> ```auto
> volumes:
> - '/container/pihole.example.com/pihole:/etc/pihole:Z'
> - '/container/pihole.example.com/dnsmasq.d:/etc/dnsmasq.d:Z'
> - '/container/pihole.example.com/logs:/var/log:Z'
> 
> ```

I'm not sure if this is causing some problems, but why are you mounting the volumes using the **`:Z`** flag?

Did you try without any flags?

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [September 25, 2022, 10:33am UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/6 "2022-09-25T10:33:16Z")

</div>

> [@sscheib](#):
>
> That's exactly what I applied already (please see the above codeblock for the `FLTCONF_PIHOLE_PTR` environment variable).

Of course - sorry for not assessing your docker-compose thoroughly enough. 🙏

> [@sscheib](#):
>
> ```auto
> [root@container pihole]# cat /container/pihole.example.com/pihole/pihole-FTL.conf 
> REPLY_ADDR4=172.31.3.47
> LOCAL_IPV4=172.31.3.47
> RATE_LIMIT=1000/60
> 
> ```

That **`REPLY_ADDR4`** line is peculiar.  
Your docker-compose shows you've correctly and exclusively provided **`FTLCONF_LOCAL_IPV4`** , which supersedes the now deprecated **`REPLY_ADDR4`** - so that line shouldn't be there at all.

This rings a bell, as we've had reports about Portainer installations holding on to environment variable values even between container rebuilds/restarts (e.g. see [Pihole Portainer/Docker 5.8.1 startup error? - #7 by ptruman](https://discourse.pi-hole.net/t/pihole-portainer-docker-5-8-1-startup-error/48722/7) or [Pihole on Docker always shows old Docker Tag value - #2 by rdwebdesign](https://discourse.pi-hole.net/t/pihole-on-docker-always-shows-old-docker-tag-value/57608/2)).

I'm not familiar with Podman, but in addition to **rdwebdesign**'s suggestion to drop the `Z` flag (which may only be required in SELinux contexts), I'd probably look for ways to clear those env vars with Podman, in case it would do something similar to Portainer.

---

<div class="post-metadata">

**Author:** ![sscheib](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/df705f/32.png) [@sscheib](https://discourse.pi-hole.net/u/sscheib)\
**Post date:** [September 25, 2022, 12:28pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/7 "2022-09-25T12:28:50Z")

</div>

@rdwebdesign I am using the Z flag to indicate a bind mount, that is private and unshared (see [https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label](https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label)). Since I am running on a RHEL machine, naturally SELinux is enabled and thus I need to provide this flag. Nevertheless, I temporarily "disabled" SELinux (using `setenforce 0`, which sets the SELinux mode to permissive, thus it is not blocking anything; it merely logs what would have been blocked) and tried running without any flags with the very same outcome, unfortunately.

@Bucking_Horn Podman is in simple terms basically docker without a daemon (in a nutshell, please see [Podman](https://podman.io/#what-is-podman-podman-is-a-daemonless-container-engine-for-developing-managing-and-running-oci-containers-on-your-linux-system-containers-can-either-be-run-as-root-or-in-rootless-mode-simply-put-alias-dockerpodman-more-details-here) for a more thorough explanation).  
I checked whether there are any environment variables within the container that should not be there anymore and also verified whether environment variables are actually getting set and applied.  
I added `SKIPGRAVITYONBOOT: 1` to my `docker-compose` file to see if pihole would react to it: Yes indeed, pihole skipped updating the gravity database on boot.  
Next, I checked which environment variables are actually available simply using `env` within the container and sorting it for better readability:

```auto
[root@container pihole]# podman exec -it pihole.example.com env | sort
container=podman
CUSTOM_CACHE_SIZE=10000
DNSMASQ_USER=pihole
FLTCONF_PIHOLE_PTR=HOSTNAMEFQDN
FTL_CMD=no-daemon
FTLCONF_LOCAL_IPV4=172.31.4.102
HOME=/root
HOSTNAME=pihole.example.com
IPv6=True
PATH=/opt/pihole:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PHP_ENV_CONFIG=/etc/lighttpd/conf-enabled/15-fastcgi-php.conf
PHP_ERROR_LOG=/var/log/lighttpd/error-pihole.log
phpver=php
PIHOLE_DOCKER_TAG=2022.09.4
PIHOLE_INSTALL=/etc/.pihole/automated install/basic-install.sh
S6_BEHAVIOUR_IF_STAGE2_FAILS=2
S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0
S6_KEEP_ENV=1
S6_OVERLAY_VERSION=v3.1.1.2
SKIPGRAVITYONBOOT=1
TERM=xterm
TZ=Europe/Berlin
[root@container pihole]# 

```

When I remove the environment variable `FLTCONF_PIHOLE_PTR: HOSTNAMEFQDN` from the `docker-compose` file and restart the container, I can see it is indeed gone:

```auto
[root@container pihole]# podman exec -it pihole.example.com env | sort
container=podman
CUSTOM_CACHE_SIZE=10000
DNSMASQ_USER=pihole
FTL_CMD=no-daemon
FTLCONF_LOCAL_IPV4=172.31.4.102
HOME=/root
HOSTNAME=pihole.example.com
IPv6=True
PATH=/opt/pihole:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PHP_ENV_CONFIG=/etc/lighttpd/conf-enabled/15-fastcgi-php.conf
PHP_ERROR_LOG=/var/log/lighttpd/error-pihole.log
phpver=php
PIHOLE_DOCKER_TAG=2022.09.4
PIHOLE_INSTALL=/etc/.pihole/automated install/basic-install.sh
S6_BEHAVIOUR_IF_STAGE2_FAILS=2
S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0
S6_KEEP_ENV=1
S6_OVERLAY_VERSION=v3.1.1.2
SKIPGRAVITYONBOOT=1
TERM=xterm
TZ=Europe/Berlin
[root@container pihole]# 

```

What I cannot tell is whether pihole makes actually _use_ of these; With `SKIPGRAVITYONBOOT` I could clearly tell that pihole honored it since it skipped updating the gravity database. For `FLTCONF_PIHOLE_PTR` I am unable to tell obviously.Technically the environment variables are there, but I don't know if they are getting used. Is there a way to determine which values have been applied to pihole's runtime configuration (possibly with source, eg: from env, from conf file, etc)?

Regarding the variable `REPLY_ADDR4` in the `pihole-FTL.conf`: That is most likely an oversight on my end, as I tried different things to apply the settings back then when I moved to a container-based install from a Raspberry Pi and must have forgotten to remove it ultimately. I removed it now from the configuration file and couldn't spot any difference, however.

Further, `S6_KEEP_ENV` caught my eye and tried setting it to it's default value (which is 0, according to [GitHub - just-containers/s6-overlay: s6 overlay for containers (includes execline, s6-linux-utils & a custom init)](https://github.com/just-containers/s6-overlay#customizing-s6-behaviour)), but then the following is seen in the container logs:

```auto
s6-rc: info: service legacy-services successfully started
Stopping pihole-FTL
pihole-FTL: no process found
Stopping pihole-FTL
pihole-FTL: no process found
Stopping pihole-FTL
pihole-FTL: no process found
Stopping pihole-FTL

```

Presumably this happens due to no environment variables being present once pihole starts and switches to the user pihole (at least that is happening according to the container logs): `[i] pihole-FTL (no-daemon) will be started as pihole`

Anyway, I am really out of ideas - your help is highly appreciated! 🙂

---

<div class="post-metadata">

**Author:** ![sscheib](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/df705f/32.png) [@sscheib](https://discourse.pi-hole.net/u/sscheib)\
**Post date:** [September 29, 2022, 11:55am UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/8 "2022-09-29T11:55:10Z")

</div>

bump, anyone that experienced the same issue?

---

<div class="post-metadata">

**Author:** ![mag](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mag/32/32404_2.png) [@mag](https://discourse.pi-hole.net/u/mag)\
**Post date:** [September 30, 2022, 12:28pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/10 "2022-09-30T12:28:22Z")

</div>

I don't want to appear precocious, but isn't this a typo?

> [@sscheib](#):
>
> _ **FLT** _CONF\_PIHOLE\_PTR=HOSTNAMEFQDN

Shouldn't it say _ **FTL** _?

---

<div class="post-metadata">

**Author:** ![PromoFaux](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/promofaux/32/1545_2.png) [@PromoFaux](https://discourse.pi-hole.net/u/PromoFaux)\
**Post date:** [October 1, 2022, 3:38pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/13 "2022-10-01T15:38:44Z")

</div>

I was typing out a reply to this comment thread, but then I saw @mag 's response and realise that everybody else (including myself) involved in this thread needs a new pair of glasses 🙂

> **Original Reply**
>
> > [@sscheib](#):
> >
> > What I cannot tell is whether pihole makes actually _use_ of these;
> 
> This function is run on every container startup:
> 
> [docker-pi-hole/src/s6/debian-root/usr/local/bin/bash\_functions.sh at a9ecd4e7a20ccdd5b404aa70169f11b938f3e70d · pi-hole/docker-pi-hole · GitHub](https://github.com/pi-hole/docker-pi-hole/blob/a9ecd4e7a20ccdd5b404aa70169f11b938f3e70d/src/s6/debian-root/usr/local/bin/bash_functions.sh#L208-L217)
> 
> Which, in turn, calls:
> 
> [docker-pi-hole/src/s6/debian-root/usr/local/bin/bash\_functions.sh at a9ecd4e7a20ccdd5b404aa70169f11b938f3e70d · pi-hole/docker-pi-hole · GitHub](https://github.com/pi-hole/docker-pi-hole/blob/a9ecd4e7a20ccdd5b404aa70169f11b938f3e70d/src/s6/debian-root/usr/local/bin/bash_functions.sh#L29-L31)
> 
> `addOrEditKeyValPair` is a helper script sourced from:
> 
> [pi-hole/advanced/Scripts/utils.sh at 7fd062c4d80a6b481ec252ba401dd37f5223f46b · pi-hole/pi-hole · GitHub](https://github.com/pi-hole/pi-hole/blob/7fd062c4d80a6b481ec252ba401dd37f5223f46b/advanced/Scripts/utils.sh#L29-L41)
> 
> So the value of `FTLCONF_PIHOLE_PTR` should definitely be making it into the config file

---

<div class="post-metadata">

**Author:** ![sscheib](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/df705f/32.png) [@sscheib](https://discourse.pi-hole.net/u/sscheib)\
**Post date:** [October 1, 2022, 4:49pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/14 "2022-10-01T16:49:53Z")

</div>

Thanks for the hint @mag. Unfortunately, it does not make any difference.  
As I stated initially, I also added the value directly to the pihole-FTL.conf (without the FTL/FLT prefix of course), but that didn't work out either.  
I hoped so much I was just too stupid to type and @mag fixed it with his eagle eyes, but unfortunately that's not the case ☹

---

<div class="post-metadata">

**Author:** ![sscheib](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/df705f/32.png) [@sscheib](https://discourse.pi-hole.net/u/sscheib)\
**Post date:** [October 1, 2022, 5:19pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/15 "2022-10-01T17:19:33Z")

</div>

So, I set up an entirely new container only to ensure that the issue is not some permissions issue or something around that lines.  
The outcome is, that the queries show up as `localhost` rather than `pihole.example.com`.  
I used the following `docker-compose.yml`:

```auto
version: "3"

services:
  pihole.example.com:
    container_name: 'pihole.example.com'
    hostname: 'pihole.example.com'
    image: 'pihole/pihole:latest'
    logging:
      driver: 'journald'
    ports:
      - "172.31.4.102:5344:53/tcp"
      - "172.31.4.102:5344:53/udp"
      - "9999:80/tcp"
    environment:
      TZ: 'Europe/Berlin'
      FTLCONF_LOCAL_IPV4: '172.31.4.102'
      FTLCONF_PIHOLE_PTR: 'HOSTNAMEFQDN'
      CUSTOM_CACHE_SIZE: '10000'
      SKIPGRAVITYONBOOT: 1
    volumes:
      - '/container/pihole.example.com/pihole:/etc/pihole:Z'
      - '/container/pihole.example.com/dnsmasq.d:/etc/dnsmasq.d:Z'
      - '/container/pihole.example.com/logs:/var/log:Z'
    restart: 'unless-stopped'
    cap_add:
      - CAP_AUDIT_WRITE
      - CAP_SYS_NICE
      - CAP_CHOWN
    deploy:
      resources:
        limits:
          memory: 2048M
        reservations:
          memory: 2048M

```

I do have the following **custom** files in `dnsmasq.d` on the guest machine:  
`99-edns.conf`:

```auto
edns-packet-max=1232

```

`99-hostname.conf`:

```auto
domain=example.com

```

`99-local_servers.conf` (domains are obfuscated):

```auto
server=/a.example.com/2.31.172.in-addr.arpa/172.31.2.1
server=/b.example.com/3.31.172.in-addr.arpa/172.31.3.1
server=/c.example.com/4.31.172.in-addr.arpa/172.31.4.1
server=/d.example.com/5.31.172.in-addr.arpa/172.31.5.1
server=/e.example.com/6.31.172.in-addr.arpa/172.31.6.1
server=/f.example.com/10.31.172.in-addr.arpa/172.31.10.3
server=/g.example.com/172.31.3.1

```

I can see that the `pihole-FTL.conf` file indeed contains the environment variables from the `docker-compose.yml` file:

```auto
#; Pi-hole FTL config file
#; Comments should start with #; to avoid issues with PHP and bash reading this file
LOCAL_IPV4=172.31.4.102
PIHOLE_PTR=HOSTNAMEFQDN

```

Unfortunately, the outcome is ultimately almost the same: `localhost` is now used instead of `pi.hole` to refer to the pihole instance.

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/9/f/9f29ab7ad142d9b5f62f960d7a7c4fd52340d22e.png)

---

<div class="post-metadata">

**Author:** ![mag](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mag/32/32404_2.png) [@mag](https://discourse.pi-hole.net/u/mag)\
**Post date:** [October 5, 2022, 4:01pm UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/16 "2022-10-05T16:01:08Z")

</div>

> [@sscheib](#):
>
> `hostname: 'pihole.example.com'`

Have you possibly already tried ommitting the fqdn notation as hostname?  
So just putting

> [@](#):
>
> `hostname: 'pihole'`

instead?  
Just an idea as I've not seen an fqdn being used as a host's name before (and do not do that myself).

---

<div class="post-metadata">

**Author:** ![sscheib](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/df705f/32.png) [@sscheib](https://discourse.pi-hole.net/u/sscheib)\
**Post date:** [October 8, 2022, 1:13am UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/17 "2022-10-08T01:13:12Z")

</div>

I just tried removing FQDN from the servicename, containername and hostname, but unfortunately, it does not change anything ☹

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [October 8, 2022, 5:21am UTC](https://discourse.pi-hole.net/t/resolve-pi-hole-localhost-as-fqdn/58136/18 "2022-10-08T05:21:36Z")

</div>

> [@sscheib](#):
>
> The outcome is, that the queries show up as `localhost`

I guess that's expected - requests originating from a loopback address (`127.0.0.1`) will always be shown as `localhost`.