# 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. > On 25 Jul 2025, at 13:56, tmberg via nsd-users <nsd-users@lists.nlnetlabs.nl> > wrote: > On 2025-07-25 11:37, Manuel Stausberg via nsd-users wrote: >> $ORIGIN 0.168.192.in-addr.arpa. > > Hm.. Nope. :( 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. > > https://starka.st/run/shm/bandwidth/tmberg/errors.txt > > /T > > -- > T > _______________________________________________ > nsd-users mailing list > nsd-users@lists.nlnetlabs.nl > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users _______________________________________________ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
