unbound-docker: I am not able to setup a srv record

I setup unbound with pi-hole and all seem to work fine.

Now what i want to achieve is create some lan dns entries so i don’t have to remember ports of all the docker service containers i am running such as portianer, plex, hass and so.

when i go into the browser and type portainer.homelab.me should go to http://192.168.1.9:9000 and similar to other services as well. all the google i did tells me i need to set srv-records in unbound, so i created an srv-records.conf and included in unbound.conf

I tried my best to put in the line for the dns entries, everything comes with error or does not work, I am that good in networking so please forgive me.

here is what i tried

_port._tcp.portainer.homelab.one.  86400 IN    SRV 0        10     9000     portainer.homelab.one.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 17 (10 by maintainers)

Most upvoted comments

Apologies for the earlier confusion with the mix up on my end.

SRV records are not something I personally use so I have limited experience here. Most of the examples I’ve seen prefix the entry with local-data. For instance:

# SRV records
# _service._proto.name. | TTL | class | SRV | priority | weight | port | target.
    local-data: "_port._tcp.portainer.homelab.one.  86400 IN    SRV 0        10     9000     portainer.homelab.one."

A prefix like that makes sense though because the a-record and ptr) in the a-records.conf file I do use require that. The forward records in the forward-zone also require prefixes.

If you confirm this is the case, I should update the example file to provide greater clarity.

MatthewVance on Aug 16, 2021