Hi! Im trying to set forward and reverse on an internal ip with nsd/unbound

Hello!

Som I am trying to set set forward and reverse ip with unbound. ( version 1.22.0-2 )

Like this:

local-data-ptr: "192.168.0.224 tMbERG_tMbERG_.224.starka.st"

local-data: "224.0.168.192.in-addr.arpa. IN PTR tMbERG_tMbERG_.224.starka.st."

Hello,

in your reverse zone:

$ORIGIN .
$TTL 2147483647
@ IN SOA ns2.starka.st. hostmaster.starka.st. (
         2025062711 ; serial, todays date + todays serial
         14400 ; refresh (3 hours)
         3600 ; retry (1 hour)
         2419200 ; expire (1 week)
         3600 ) ; minimum (1 day)
         NS ns2.starka.st.
$ORIGIN 0.168.192.in-addr.arpa.
#100 PTR host1.example.lan.
224 PTR tMbERG_tMbERG_.224.starka.st.

I *think* the origin is wrong?
My guess is that this should be

$ORIGIN 0.168.192.in-addr.arpa.

Hope that helps.

But no matter what I do. Either the zonefiles has error or unbound/nsd refuse to start. :frowning:

Ive tried this a few times now. And yes i have googled, and tried several things. But no go. :[

It is very helpful to include *what* exactly you have tried, and what the resulting errors were :wink:

Best,
Manuel

Hm.. Nope. :frowning:

https://starka.st/run/shm/bandwidth/tmberg/224.0.168.192.in-addr.arpa.zone.txt

https://starka.st/run/shm/bandwidth/tmberg/tMbERG_tMbERG_.224.starka.st.zone.txt

https://starka.st/run/shm/bandwidth/tmberg/errors.txt

/T

# you are using hash sign for comments in zone files.
; BIND, NSD (and other DNS software) uses semicolon

this is why server refuses to use your zones.

$ORIGIN 0.168.192.in-addr.arpa.

Hm.. Nope. :frowning:

the $ORIGIN should be used once on top and then
you can refer to zone top as @ and use relative names:

https://starka.st/run/shm/bandwidth/tmberg/224.0.168.192.in-addr.arpa.zone.txt

$ORIGIN 0.168.192.in-addr.arpa.
@ SOA 224 224.0.168.192.in-addr.arpa.(
        2025062711 ; serial, todays date + todays serial
        14400 ; refresh (3 hours)
        3600 ; retry (1 hour)
        2419200 ; expire (1 week)
        3600 ; minimum (1 day)
  )
; your SOA should have contact email but not critical
@ NS ns2.starka.st.
;#100 PTR host1.example.lan.
224 PTR tMbERG_tMbERG_.224.starka.st.

https://starka.st/run/shm/bandwidth/tmberg/tMbERG_tMbERG_.224.starka.st.zone.txt

likewise here.

Hi,

https://starka.st/run/shm/bandwidth/tmberg/224.0.168.192.in- addr.arpa.zone.txt

Index of /run/shm/bandwidth/tmberg/ tMbERG_tMbERG_.224.starka.st.zone.txt

https://starka.st/run/shm/bandwidth/tmberg/errors.txt

the links are the same as before, but the files now look different...
Would be easier if you just include them here :slight_smile:

Btw. there seems to be no "errors.txt", I just see "tmberg" on that page.

Best,
Manuel

It works now.

But still when sending to for example: https://www.mail-tester.com/

I see:

Received: from [192.168.0.224] (tMbERG_tMbERG_.224.starka.st [192.168.0.224])
  by mx.starka.st (mx.starka.st) with ESMTP id C46691BA5C
  for <test-pu6fpd2ay@srv1.mail-tester.com>; Thu, 31 Jul 2025 17:48:33 +0200 (CEST)

But maybe I got this wrong. I want it to be:

Received: from [tMbERG_tMbERG_.224.starka.st] (tMbERG_tMbERG_.224.starka.st [tMbERG_tMbERG_.224.starka.st])
         by mx.starka.st (mx.starka.st) with ESMTP id C46691BA5C
         for <test-pu6fpd2ay@srv1.mail-tester.com>; Thu, 31 Jul 2025 17:48:33 +0200 (CEST)

But thats not possible?

Im realying via my isp.

/T

It loads and work. But as I said in my previous mail.

I want it to look like:

Received: from [tMbERG_tMbERG_.224.starka.st] (tMbERG_tMbERG_.224.starka.st [tMbERG_tMbERG_.224.starka.st])
         by mx.starka.st (mx.starka.st) with ESMTP id C46691BA5C
         for <test-pu6fpd2ay@srv1.mail-tester.com>; Thu, 31 Jul 2025 17:48:33 +0200 (CEST)

When sending mail. ( for example )

Instead of:

Received: from [192.168.0.224] (tMbERG_tMbERG_.224.starka.st [192.168.0.224])
         by mx.starka.st (mx.starka.st) with ESMTP id C46691BA5C
         for <test-pu6fpd2ay@srv1.mail-tester.com>; Thu, 31 Jul 2025 17:48:33 +0200 (CEST)

But can it be done?

Realying via my isp.

/T

Hi,

I am not sure I understand what you are trying to do, and I know basically nothing about configuring mailservers, so take everything I say with a grain of salt...

Correct me if I'm wrong, but it looks like you are trying to set up reverse pointers for addresses in the 192.168.0.0/16 address space, which (apart from local testing of course) does not make a lot of sense

This address block is reserved for private use, and the corresponding name space in the DNS (168.192.in-addr.arpa.) is controlled by IANA.

So, you can of course create a zonefile with reverse pointers, it's just that no resolver will ask _your_ nameservers, they will ask IANA's nameservers.

Looking at the discussion, it feels a bit like we are dealing with a X/Y Problem (see xyproblem.info)- what exactly is it you are trying to achieve?

Best,
Manuel

Hello!

Sorry. I forgot to mention that Postfix/Unbound/Nsd is running on the same box.

Since its the same box I was thinking. Its all originating from the same system. It could be "fun". And because I can. ( Well... )

Setting it like that.

Thats it!

/T

The standard "from" part of the header is either:

Received: from HELO-STRING (HOSTNAME [IP-ADDRESS]) by ....

or:

Received: from HELO-STRING (IP-ADDRESS) by ....

So, it seems like your reverse DNS is fine, but your mail client isn't
sending the correct "HELO" string.

Also, you can't avoid the IP address appearing unless you reconfigure
postfix itself to behave in a non-standard way:

https://www.pobox.help/hc/en-us/articles/1500000193602-The-elements-of-a-Received-header

So, you just need to fix your mail client!

P.S. "HELO" string can also be "EHLO" string, and is basically the client greeting.

Cheers, Jamie

Thank you very much!

/T