A-Records.conf Not working

[bigverm23]

sorry to open an issue, but I dont understand why the second entry is not resolving properly

A Record

local-data: "officepc.local. A 10.0.0.12"
local-data: "kenphone.local. A 10.0.0.190"

PTR Record

local-data-ptr: "10.0.0.12 officepc.local."
local-data-ptr: "10.0.0.190 familyroomtv.local."

[MatthewVance]

Is there a reason the names for the second A record and second PTR don’t match?

On Oct 4, 2021, at 9:52 AM, bigverm23 @.***> wrote:

 sorry to open an issue, but I dont understand why the second entry is not resolving properly

A Record

local-data: "officepc.local. A 10.0.0.12" local-data: "kenphone.local. A 10.0.0.190" PTR Record

local-data-ptr: "10.0.0.12 officepc.local." local-data-ptr: "10.0.0.190 familyroomtv.local." — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[bigverm23]

that's a good question. I updated it, restarted unbound...same result

A Record

local-data: "officepc.local. A 10.0.0.12"
local-data: "familyroomtv.local. A 10.0.0.190"

PTR Record

local-data-ptr: "10.0.0.12 officepc.local."
local-data-ptr: "10.0.0.190 familyroomtv.local."

; <<>> DiG 9.16.8-Ubuntu <<>> @10.0.0.190 familyroomtv.local ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

top option works:

; <<>> DiG 9.16.8-Ubuntu <<>> @10.0.0.12 officepc.local ; (1 server found) ;; global options: +cmd ;; Got answer: ;; WARNING: .local is reserved for Multicast DNS ;; You are currently testing what happens when an mDNS query is leaked to DNS ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18967 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION: ;officepc.local. IN A

;; ANSWER SECTION: officepc.local. 10 IN A 10.0.0.12

;; Query time: 0 msec ;; SERVER: 10.0.0.12#53(10.0.0.12) ;; WHEN: Tue Oct 05 08:29:58 EDT 2021 ;; MSG SIZE rcvd: 48