Need someone else to check and verify something

[nightshade00013]

I have a plugin jail setup with a Transmission and a VPN. Have ALWAYS had problems with Transmission connecting to trackers. Was messing around today and saw one that worked ok and it was set to an IP address. It got me to thinking and so I modified a few others as well to change an existing tracker to a ip rather than hostname and it was then able to connect. Went in and looked inside of the jail at etc/resolv.conf and the nameservers are set as only IPv6 so I added in a nameserver as 8.8.8.8 and low and behold the trackers started connecting properly.

So I wanted to see if anyone else was having the same issue/config setup as what I am seeing. I don't know if this is a flaw in a config somewhere that a nameserver is not being transported over to the jails or if this is supposed to happen. I did notice that it would eventually resolve a hostname in the jail if I did a ping but it was VERY slow in doing so and I checked a standard jail as well as the plugin jail and they both showed the same thing.

 

[Allan Wilmath]

It sounds like your DNS settings for the jail are missing. You need to have a DNS server configured inside the jail, the jail network settings. Use 8.8.8.8 if you need something easy to remember.

Also, if you are going to setup a VPN on your home network, DO NOT use 192.168.x.x, instead use something weird like 10.100.10.x. This is because of routing, if the network you are initialing a VPN overlaps the one you are connecting to, you will have issues with the client sending VPN traffic to the local network instead of the VPN tunnel. Everything will look like it is working, but you won't be able to connect to the remote network hosts.

 

[nightshade00013]

The FreeNAS system has DNS settings setup correctly, the jail is setup to DHCP and is getting autoconf IPv6 addresses. To add to that there is no place in the GUI to setup the DNS servers but what is configured as the system default should be translated into the jail from my understanding I am also using three different DNS servers in the system of which only one is in my local range.

I have my network setup in the 10.X.X.X range already and it is not conflicting with the VPN. I agree that the DNS settings are missing but that is from the onset of the jail configuration and this is universal across the jails.


BTW this is what I am getting for a /etc/resolv.conf which has no IPv4 addresses. After adding one in before a reboot of the jail it is then removed after restarting a jail so this is being reconfigured after a reboot of the jail by the system. I want to verify this action before I file a ticket unless this is working by design. The first nameserver it is generating is my router.

Code:

# Generated by resolvconf
search home.*****.net
nameserver 2600:8803:e600:36:xxx:xxx:xxx:xxx
nameserver 2001:4860:4860::8888
nameserver 2620:0:ccc::2

I setup a brand new fresh jail and checked it with default settings and got the exact same /etc/resolv.conf file even though the system is:

 

[dlavigne]

What's the build version (from System -> Information)? And did you install jails fresh starting in the 9.10 series or upgrade them from earlier versions (such as 9.3)?

 

[nightshade00013]

@dlavigne


FreeNAS-9.10.2-U1 (86c7ef5)

This is an upgrade from 9.3 but has pretty much been sequentially upgraded as they have come along.

I had jails originally from 9.3 but did a fresh jail after 9.10 was installed.

 

[Allan Wilmath]

I consoled in to my Plex jail and added 8.8.8.8 to the /etc/resolve.conf file and then restarted. The changes survived the restart. By default I only had one entry, my router's IPv4 address. I have no IPv6 entries, but then I think I did not enable IPv6 in the first place.

 

[nightshade00013]

Ok, searched around a bit and this seems to be a bug that has been popping up for a while now at times.

https://forums.freenas.org/index.php?threads/wrong-nameserver-in-jails.22286/

https://forums.freenas.org/index.php?threads/jails-lose-name-resolution-dns-after-restart.27527/

Since I use DHCP but something seems to be weird somewhere it was pulling ONLY the ipv6 addresses and overwriting anything I put in manually and save. I poked around and found a solution that will work for now with no problems. I edited the file and put public ipv6 and ipv4 dns servers so as long as access to an external DNS is not restricted they should have access. I then ran:

Code:

chflags schg resolv.conf

This locked the file and prevents changes from being made unless I manually unlock it. This will serve my purposes until a later point in time in which I likely do a fresh install of FreeNAS 10 when it is finalized.