I met the same issue, sizeToFit also can't work on Big Sur.
lesterhan
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Singapore
Post
Replies
Boosts
Views
Activity
Any advice is greatly appreciated.
This is a defect in NSURLSession API, confirmed by Apple.
Hi eskimo, we use packet tunnel provider.
I think DNS is well configured.
On worked macOS 13.2.1, the interface details and DNS settings like below:
ifconfig en0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=50b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV,CHANNEL_IO>
ether 14:9d:99:7a:63:8a
inet6 fe80::f9:3d3a:cf03:a052%en0 prefixlen 64 secured scopeid 0x8
inet 10.12.25.199 netmask 0xfffffe00 broadcast 10.12.25.255
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (1000baseT <full-duplex>)
status: active
scutil --dns
resolver #1
search domain[0] : dhcp.xxxx.net
nameserver[0] : 192.19.189.30
if_index : 8 (en0)
flags : Scoped, Request A records
reach : 0x00000002 (Reachable)
On macOS 14.0 beta 5, the interface and DNS have same settings as 13.2.1, but after tunnel provider connected, nslookup command always timeout.
ifconfig en0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=50b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV,CHANNEL_IO>
ether 14:98:77:2e:c8:89
inet6 fe80::1485:6060:796d:4828%en0 prefixlen 64 secured scopeid 0x9
inet 10.12.25.44 netmask 0xfffffe00 broadcast 10.12.25.255
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (1000baseT <full-duplex>)
status: active
scutil --dns. (same output before and after enable the tunnel provider)
resolver #1
search domain[0] : dhcp.xxxx.net
nameserver[0] : 192.19.189.30
if_index : 9 (en0)
flags : Scoped, Request A records
reach : 0x00000002 (Reachable)
Also on same machine(macOS 14.0 beta 5), if use a USB adapter, then DNS works well. The adapter interface details:
en7: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=6464<VLAN_MTU,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether c4:41:1e:75:91:16
inet6 fe80::406:dbc8:b9d0:3bd%en7 prefixlen 64 secured scopeid 0xe
inet 10.12.25.68 netmask 0xfffffe00 broadcast 10.12.25.255
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (1000baseT <full-duplex>)
status: active
resolver #1
search domain[0] : dhcp.xxxx.net
nameserver[0] : 192.19.189.30
if_index : 14 (en7)
flags : Scoped, Request A records
reach : 0x00000002 (Reachable)
DNS requests will not go though the tunnel provider. We have a proxy provider to check the domain name to determine whether the corresponding traffic goes through the tunnel.