Messages

I did a bunch of reading and that's fine.  It isn't DNS though.   Not everything supports that natively today.   

What do we need to do to have it work with the local DNS I have running on opnsense is the goal so it's a single source of truth to manage and consistently maintain versus broadcast traffic approaches of zeroconf?   

I'd like to be able to SSH/RDP to hosts that have dynamic IP assignments and not need to hunt down what the IP is today.   

IPv4 works just fine.   IPv6 is my learning opportunity. 

I don't plan to setup static addresses with IPv6 unless I "have" to and I only do that for catch 22 scenarios such as my storage server, which hosts my DNS system, so for other systems as they come up to mount NFS/SMB mounts, they need to use the IP as DNS might not be up yet in the case of total environment power failure.   Otherwise I use the DNS names for 99% of the things that I do.   

I'd like to be able to use IPv6 with DNS names effectively.   

I haven't heard of multi-cast DNS.  Is there somewhere I can dig into that more that you'd recommend in the meantime?   Is that a pretty common setup for IPv6 internal networks?   Is it supported across most if not all OS? 

I've setup my system with Opnsense 20.7, then updated to 20.7.7 & then did the patch fix for unbound stability issue of 1.13.0_1.   

My external interface is Spectrum linked.  I've setup prefix delegation of a /60 and that appears to be working. 
Internal interface is configured with Track interface.  The configuration type is "DHCPv6" & I've tried "Track Interface" also.   

I'm using unbound DNS with DHCP registration checked. 

All my client machines are getting proper IPv6 addresses and things appear to be working mostly correctly. 

When I configured a new box, it got the proper internal IPv6 address from DHCPv6.   Yet when I do a dig newmachine.home.mine.org or dig aaaa newmachine.home.mine.org it only returns an A record.

The question I have is what do I need to do to be able to have my IPv6 addresses that get assigned out (either via SLAAC or DHCPv6) to be registered as AAAA addresses in DNS?

What am I missing here? 

I did the update command:  pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz

It took about 10 mins to execute, something strange is going on here.   Everything else outside this instance is near instant response.   Things to do the pkg or other update checking is slow.  for example, checking for updates or plugin updates.   

Any ideas?   

I'm attempting to revert the unbound back to version 20.7.6 and it doesn't appear to work for me.  This is a new install into a VMware image from the 20.7 ISO file then updated to 20.7.7 immediately afterwards.   I log in via SSH or the console then hit 8 to go to shell. 

Then when I run

Code Select Expand

opnsense-revert -r 20.7.6 unbound I get the following:

Code Select Expand

root@opnsense:~ # opnsense-revert -r 20.7.6 unbound
Fetching unbound.txz: ............................... failed


if I run

Code Select Expand

curl -o unbound.txz http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD%3A12%3Aamd64/20.7/MINT/20.7.6/OpenSSL/Latest/unbound.txz
it takes about 10 seconds and it's done.   

What do I need to look at to figure out what's going on here?