Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
22.7 Legacy Series
»
Debug where a Unbound RR is originating?
« previous
next »
Print
Pages: [
1
]
Author
Topic: Debug where a Unbound RR is originating? (Read 6328 times)
janjoh
Newbie
Posts: 5
Karma: 0
Debug where a Unbound RR is originating?
«
on:
July 28, 2022, 05:55:36 pm »
So, I started a thread here
https://forum.opnsense.org/index.php?topic=29394.0
The I figured I'd upgrade to 22.7 but I have the same thing.
Basically, there is a "ghost RR" that I can not figure out where it originates.
I used to run home assistant in docker on a machine on my network. Now breaking it out to dedicated hardware.
But I can not get rid of the .30 RR
It is not in the override of Unbound when looking in the web UI.
It is not in the public DNS servers.
If i actually ADD the proper record to Unbound override, I will have both the 210 and 30 RR.
How can i figure out where in the world is this record originating?
root@OPNsense:~ # unbound-control -c /var/unbound/unbound.conf list_local_data | grep home
esphome.mupp.net. 3600 IN A 172.25.74.30
homeassistant.mupp.net. 3600 IN A 172.25.74.30
home.arpa. 10800 IN NS localhost.
home.arpa. 10800 IN SOA localhost. nobody.invalid. 1 3600 1200 604800 10800
30.74.25.172.in-addr.arpa. 3600 IN PTR esphome.mupp.net.
30.74.25.172.in-addr.arpa. 3600 IN PTR homeassistant.mupp.net.
root@OPNsense:~ #
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
22.7 Legacy Series
»
Debug where a Unbound RR is originating?