commit | 3f5ee02fdc991e253e243d60440e64ecda019c8f | [log] [tgz] |
---|---|---|
author | Mike Yu <yumike@google.com> | Tue Aug 17 15:53:44 2021 +0800 |
committer | Mike Yu <yumike@google.com> | Tue Aug 17 08:40:51 2021 +0000 |
tree | 97f0c09b344c72c9a2f3a7a0bf3431479260d657 | |
parent | b6e255d10a5e9e6d7fb88c348fee0103fde1ae1b [diff] |
Remove the confusing log in getPrefix64 This log can sometimes confuse people. A common case where this log is printed is that an app specifies AF_UNSPEC but there are no resolved IPv6 addresses for the hostname. ResolverController: No valid NAT64 prefix (106, <unspecified>/0) After this change, the resolver logs will still be enough for us to infer if DNS64 synthesis is performed. Bug: 196888805 Test: build dnsresolver pass Change-Id: Ic06299d1a0c6526e7ed1a0a418a8da19dbf2b6da
This code uses LOG(X) for logging. Log levels are VERBOSE,DEBUG,INFO,WARNING and ERROR. The default setting is WARNING and logs relate to WARNING and ERROR will be shown. If you want to enable the DEBUG level logs, using following command. adb shell service call dnsresolver 10 i32 1 VERBOSE 0 DEBUG 1 INFO 2 WARNING 3 ERROR 4 Verbose resolver logs could contain PII -- do NOT enable in production builds.