Hostname didn't work

TrueNAS General
1

I have set my hostname under Network like you can see in the picture.

2025-10-28_20-59
2025-10-28_20-59573×269 13.4 KB

But unfortunately it doesn’t seems to work.
When I track the dns treuenas shows under the default? Hardware name.

$ ping GL-SFT1200.lan
PING GL-SFT1200.lan (192.168.2.5) 56(84) bytes of data.
64 bytes from GL-SFT1200.lan (192.168.2.5): icmp_seq=1 ttl=64 time=0.392 ms

Any ideas? I already had rebooted everything involved.

Second thing is, that truenas is trying to resolve nextcloud-aio-nextcloud.
I once installed nextcloud-aio-nextcloud via Apps. But that is several days ago and it is deinstalled already. I came across this as I tried to figure out the hostname thing.

2025-10-28 21:01:45  GL-SFT1200.lan  A  nextcloud-aio-nextcloud.  Drop  Local  SERVFAIL  0ms  1761681763
2

Can you please try rephrasing your question.

The hostname in the screenshot does not match the one you pinged. I am not sure what you are trying to do and what the outcome was or how that outcome wasn’t what you expected or wanted.

As an aside, do you have any local DNS resolution set up so that clients on your LAN can find out what IP to visit when going to hostname x?

3

What happens when you ping NAS-0 ?
What is your local DNS server ?

4

I’m not entirely sure, but it could be that ping NAS-0.lan would only work if your NAS is getting its IP from DHCP. It depends on your router dns resolver actually.

5

Sorry, I forgot my code for the ping to nas-0.
It is not reachable.
But DHCP could be the Awnser. Truenas had a static IP. But why did the Router have GL-SFT1200 as hostname?

6

Have no idea.

Also .local is reserved for mDNS, so ping NAS-0.local may work.

7

Does it look like this?

sft1200_1
sft1200_11000×1000 51 KB

If so, that’s its model name…

8

Jep, I have found an old static Mapping in my DHCP I didn’t remembered and did’t found in first place.
So the DNS Problem is solved… THX a lot.
Anyway. I have this.
I installed Nexcloud a while ago for perhaps 2h…

grafik
grafik1089×411 106 KB

9

… I rebooted --everything–. Til now the Problem seems disappeared…
Perhaps it was only …a miracle? Sorry for wasting your time…

2 Likes
10

… I spoke too soon. Yesterday I forgot to unlock the datasets. After I saw the errors on a Backup I unlocked the Datasets and shortly after that I received the SERVFAIL for nextcloud-aio-nextcloud. again. Interesting on that is, its IPv6 mostly. But IPv6 is disabled in my Network… Mostly.

grafik
grafik1180×498 124 KB

You can see the impact on my Network (Green Dots are NAS-0):

grafik
grafik1149×774 108 KB

11

There are more Datapoints…

The second I unset the pool in Apps the queries stops immediately and is right back if I choose the pool again. Seems docker hat some hidden fragments of the nextcloud install… How can I clean that…. Simply by deleting the directory’s

12

Sorry for my delay…

The task to delete nextcloud left all containers running on truenas…

# docker ps --format '{{.ID}} {{.Names}} {{.Image}} {{.Ports}}'

6db79f67f739 nextcloud-aio-apache ghcr.io/nextcloud-releases/aio-apache:latest 80/tcp, 0.0.0.0:11000->11000/tcp, :::11000->11000/tcp
2d81c8479a5c nextcloud-aio-nextcloud ghcr.io/nextcloud-releases/aio-nextcloud:latest 9000/tcp
f066b9dca11d nextcloud-aio-imaginary ghcr.io/nextcloud-releases/aio-imaginary:latest 
7dd08a9034fe nextcloud-aio-redis ghcr.io/nextcloud-releases/aio-redis:latest 6379/tcp
2da698ed9eff nextcloud-aio-database ghcr.io/nextcloud-releases/aio-postgresql:latest 5432/tcp
313fb3b6b457 nextcloud-aio-whiteboard ghcr.io/nextcloud-releases/aio-whiteboard:latest 3002/tcp
120a095885c6 nextcloud-aio-notify-push ghcr.io/nextcloud-releases/aio-notify-push:latest 
9a6c8f36d1b2 nextcloud-aio-talk ghcr.io/nextcloud-releases/aio-talk:latest 0.0.0.0:3478->3478/tcp, 0.0.0.0:3478->3478/udp, :::3478->3478/tcp, :::3478->3478/udp
7161e837fabc nextcloud-aio-collabora ghcr.io/nextcloud-releases/aio-collabora:latest 9980/tcp
609d651cb978 nextcloud-aio-mastercontainer nextcloud/all-in-one:latest 80/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp
root@NAS-0[/home/truenas_admin]# docker stop nextcloud-aio-apache nextcloud-aio-nextcloud nextcloud-aio-imaginary nextcloud-aio-redis nextcloud-aio-database nextcloud-aio-whiteboard nextcloud-aio-notify-push nextcloud-aio-talk nextcloud-aio-collabora nextcloud-aio-mastercontainer
nextcloud-aio-apache
nextcloud-aio-nextcloud
nextcloud-aio-imaginary
nextcloud-aio-redis
nextcloud-aio-database
nextcloud-aio-whiteboard
nextcloud-aio-notify-push
nextcloud-aio-talk
nextcloud-aio-collabora
nextcloud-aio-mastercontainer
root@NAS-0[/home/admin]# docker ps -a | awk '/nextcloud-aio|nextcloud\/all-in-one/ {print $1}' | xargs -r docker stop
6db79f67f739
2d81c8479a5c
f066b9dca11d
7dd08a9034fe
2da698ed9eff
313fb3b6b457
120a095885c6
9a6c8f36d1b2
7161e837fabc
609d651cb978
root@NAS-0[/home/admin]# docker ps -a | awk '/nextcloud-aio|nextcloud\/all-in-one/ {print $1}' | xargs -r docker rm
6db79f67f739
2d81c8479a5c
f066b9dca11d
7dd08a9034fe
2da698ed9eff
313fb3b6b457
120a095885c6
9a6c8f36d1b2
7161e837fabc
609d651cb978
root@NAS-0[/home/admin]# docker network ls | grep -i nextcloud | awk '{print $1}' | xargs -r docker network rm
a059456e49fa
0b2ef3e73224
root@NAS-0[/home/admin]# docker volume ls | grep -i nextcloud | awk '{print $2}' | xargs -r docker volume rm
nextcloud_aio_apache
nextcloud_aio_database
nextcloud_aio_database_dump
nextcloud_aio_mastercontainer
nextcloud_aio_nextcloud
nextcloud_aio_redis