Jails on Core 13.0-U5.2 do not connect to the internet

[BuffTofu]

Hi,

I have 2 jails on my NAS that ran perfectly fine before I updated to 13.0-U5.2, and now pinging google.com doesn't work despite no changes being made. I s the answer right in front o me or is this a major bug?

Thanks!

 

[winnielinnie]

Can you ping 8.8.8.8

 

[BuffTofu]

Can you ping 8.8.8.8

Yes. So it is a DNS problem then?

 

[BuffTofu]

Can you ping 8.8.8.8

Here are my settings.

I have Xfinity and the 75... is what my router uses

 

[winnielinnie]

So it is a DNS problem then?

Looks like it.

Can you ping google.com from TrueNAS directly?

 

[BuffTofu]

Looks like it.

Can you ping google.com from TrueNAS directly?

Yes. Just a jail problem

 

[winnielinnie]

Within the jail:

Code:

resolvconf -l

 

[BuffTofu]

Within the jail:

Code:

resolvconf -l

Both show nothing...

 

[winnielinnie]

Is the resolver configured under the jail's Network Properties?

 

[BuffTofu]

Is the resolver configured under the jail's Network Properties?

I

Is the resolver configured under the jail's Network Properties?

Yes. The directory is in the jail, right? Not the base system.

 

[winnielinnie]

You can manually enter each nameserver line in the jail's "resolver" text field under Network Properties. Or write the word none to inherit the TrueNAS system's resolver.

 

[BuffTofu]

That doesn't change anything, unfortunately.

 

[winnielinnie]

If you set it to "none", you still have no output when running resolvconf -l in the jail?

 

[BuffTofu]

If you set it to "none", you still have no output when running resolvconf -l in the jail?

Still nothing

 

[winnielinnie]

Not sure why an update to 13.0-U5.2 would break your jail's DNS.

Usually the jail will just adopt your host's nameservers.


@Patrick M. Hausen or @Jailer any ideas?

• No DNS resolution in their jails after updating to TrueNAS Core 13.0-U5.2.
• resolvconf -l shows nothing in the jail.
• Setting the resolver option to "none" in the jail's network properties does not inherit the host's nameservers.
• Jails can only ping IP addresses; not websites or domain names.

 

[winnielinnie]

What about manually typing in /etc/resolv.conf as the value for "resolver" under Network Properties?

 

[BuffTofu]

What about manually typing in /etc/resolv.conf as the value for "resolver" under Network Properties?

That’s what it has been the whole time

 

[Patrick M. Hausen]

The domain and search entries in the screenshot above are nonsense. But that should not keep name resolution from working. Is 192.168.0.1 your router? Could you put nameserver 192.168.0.1 in your jail's resolver field and try again? Why don't you use your router as the recursive namerserver for all local devices in the first place?

 

[BuffTofu]

The domain and search entries in the screenshot above are nonsense. But that should not keep name resolution from working. Is 192.168.0.1 your router? Could you put nameserver 192.168.0.1 in your jail's resolver field and try again? Why don't you use your router as the recursive namerserver for all local devices in the first place?

I put it into the resolver and it did nothing. I reconfigured the base nameservers and set the jails to recursive and it also did nothing. It worked totally fine before the update. Anything I can screenshot to help?

 

[Patrick M. Hausen]

"When in doubt, use tcpdump."

(unknown network engineer, possibly me )