And the actual database file db.50.168.192.in-addr.arpa:
**$TTL 604800
@ IN SOA dns.nibbles.hom. admin.nibbles.hom. (
3 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
; name servers - NS records
@ IN NS dns.nibbles.hom.
; PTR records
4 IN PTR dns.nibbles.hom.
3 IN PTR sexi01.nibbles.hom.
2 IN PTR ipmi01.nibbles.hom.
**
I believe there is a plugin for CoreDNS that would take care of generating PTR records based on the regular zone file contents but I don't need that for the few servers I am running and I couldn't understand the documentation ( seems like you need a better understanding of CoreDNS than I can get in an hour ).
Thanks for that Rob. Got me over the hump. Just want to add in PTR records and I will be golden.
I found that I needed the following for reverse lookup on a subnet 192.168.50.0/24:
In the Corefile:
50.168.192.in-addr.arpa {
file /root/db.50.168.192.in-addr.arpa
log
errors
}
And the actual database file db.50.168.192.in-addr.arpa:
**$TTL 604800
@ IN SOA dns.nibbles.hom. admin.nibbles.hom. (
3 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
; name servers - NS records
@ IN NS dns.nibbles.hom.
; PTR records
4 IN PTR dns.nibbles.hom.
3 IN PTR sexi01.nibbles.hom.
2 IN PTR ipmi01.nibbles.hom.
**
I believe there is a plugin for CoreDNS that would take care of generating PTR records based on the regular zone file contents but I don't need that for the few servers I am running and I couldn't understand the documentation ( seems like you need a better understanding of CoreDNS than I can get in an hour ).
Does anyone know if you can use such external plugins with the normal coreDNS-Dockerimage?