diff options
| author | Mike Yu <yumike@google.com> | 2021-08-17 15:53:44 +0800 |
|---|---|---|
| committer | Mike Yu <yumike@google.com> | 2021-08-17 08:40:51 +0000 |
| commit | 3f5ee02fdc991e253e243d60440e64ecda019c8f (patch) | |
| tree | 97f0c09b344c72c9a2f3a7a0bf3431479260d657 /ResolverController.cpp | |
| 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
Diffstat (limited to 'ResolverController.cpp')
| -rw-r--r-- | ResolverController.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/ResolverController.cpp b/ResolverController.cpp index 9e693d31..2f143f5d 100644 --- a/ResolverController.cpp +++ b/ResolverController.cpp @@ -294,8 +294,6 @@ void ResolverController::stopPrefix64Discovery(int32_t netId) { int ResolverController::getPrefix64(unsigned netId, netdutils::IPPrefix* prefix) { netdutils::IPPrefix p = mDns64Configuration.getPrefix64(netId); if (p.family() != AF_INET6 || p.length() == 0) { - LOG(INFO) << "No valid NAT64 prefix (" << netId << ", " << p.toString().c_str() << ")"; - return -ENOENT; } *prefix = p; |