Bind 9 in Jail Stopped Working

[wgreenway]

This is a really weird thing. I'm on FreeNas 11.3 I had three jails set up... 2 bind nameservers and 1 dhcp server.

Out of the blue for no reason I can determine, the nameserver jails became unreachable.

I created the jails with really basic commands:

iocage create --name nsserveralpha --release 13.1-RELEASE
iocage set ip4_addr="ix0|192.168.0.2/24" nsserveralpha
iocage set defaultrouter=192.168.0.1 nsserveralpha
iocage start nsserveralpha
iocage console nsserveralpha
pkg update
pkg install bind914

configure the rc.conf and bind configuration and prosper.

This worked MULTIPLE times and I cloned the jail and it worked flawlessly.

Now, I can go through those steps. The name server INSIDE the jail can resolve hosts. Everything trying to connect on 192.168.0.2 just times out. I can ping the jail from another host but DNS doesn't fly.

I've experimented with enabling allow_raw_sockets and allow_socket_af but can't get back to what used to work.

It shows the jail on ix0 nic:

This is inside the jail.

Ideas, suggestions?

 

[wgreenway]

Bump... I'd really like to get this functionality back. Since I'm unable to view VMs because of some other bug, I'd like to get this working again.

 

[wgreenway]

Okay apparently this was an RC2 issue... it appears to be fixed in 11.3-U1.