The one place for your designs
To enable design management, you'll need to meet the requirements. If you need help, reach out to our support team for assistance.
Some /e/ services still using 8.8.8.8 DNS
Some /e/ services still using 8.8.8.8 DNS
Summary
While checking traffic using Wireshark one can notice 8.8.8.8 is still used by some OS parts, even when another DNS is set (9.9.9.9)
Steps to reproduce
Enforce DNS to 9.9.9.9
What is the current behavior?
Calls to 8.8.8.8 calls noticed
What is the expected correct behavior?
No more calls to 8.8.8.8 or other Google DNS
Relevant logs and/or screenshots
06-04 17:32:23.294 19283 19341 I System.out: Level_1 : Socket
<0xe15dfe00> try to connect now.
06-04 17:32:23.294 19283 19341 I System.out: Level_1 : Socket
<0xe15dfe00> being dispatching to <tmsg.intsig.net:443>.
06-04 17:32:23.295 19283 19341 E libc : Access denied finding
property "net.dns1"
06-04 17:32:23.296 19283 19341 E libc : Access denied finding
property "net.dns2"
06-04 17:32:23.296 19283 19341 I System.out: Level_1 : Add default dns
server: 8.8.8.8 & 8.8.4.4
06-04 17:32:23.308 19283 19341 I System.out: Level_1 : Socket
<0xe15dfe00> resolved one dns 0x11f53778 - 120.55.245.17.
06-04 17:32:23.308 19283 19341 I System.out: Level_1 : Socket
<0xe15dfe00> try to connect port 443 with timeout 3.
06-04 17:32:23.310 19283 19340 I System.out:
ChannelSDK:channelDidResolveDNS 120.55.245.17
06-04 17:32:23.780 19283 19341 I System.out: Level_1 : Socket
<0xe15dfe00> did connected to host <tmsg.intsig.net:443>.
06-04 17:32:23.782 19283 19340 I System.out: Level_1 : Channel
DPSMessage did connected to host.
Possible fixes
(If you can, link to the line of code that might be the cause for this problem)