safe search reporting wrong google IPv6 address on clients

242 views
Skip to first unread message

l4k3k3m4n

unread,
Aug 31, 2018, 2:43:44 AM8/31/18
to NxFilter
Hello,
I recently started to implement IPv6 and encountered a problem with google safe search.

I have enabled safe search on the policy in strict mode.


When I lookup www.google.com on the nxfilter itself everything looks right:

uadm@ns01:~$ nslookup www.google.com 10.3.55.66
Server:         10.3.55.66
Address:        10.3.55.66#53

Non-authoritative answer:
Address: 216.239.38.120
Address: 2001:4860:4802:32::78



When I nslookup on a windows client the IPv4 is correct but the IPv6 is not:

C:\Windows\System32>nslookup www.google.com 10.3.55.66
Server:  UnKnown
Address:  10.3.55.66

Nicht autorisierende Antwort:
Name:    www.google.com
Addresses:  2a00:1450:4001:821::2004
          216.239.38.120


So why is there no information that this is a CNAME alias? It should be there I think? At least I can see it on other lookups with CNAME.

And the IPv6 is wrong, it is not the safe search IP.


What could be the problem?
Thanks a lot.

Cheers.

Jahastech

unread,
Aug 31, 2018, 2:50:15 AM8/31/18
to NxFilter
At the moment, we only redirect it when it's an A type query. But we will work on it for IPv6.

l4k3k3m4n

unread,
Aug 31, 2018, 4:30:51 AM8/31/18
to NxFilter
Any idea when this will be available?

So the temporary solution for me would be to place a custom zone file for www.google.com with A and AAAA records from forcesafesearch.google.com ?

Thanks a lot.
Cheers

Jahastech

unread,
Aug 31, 2018, 4:41:37 AM8/31/18
to NxFilter
Maybe next month. Why is it so urgent to you? Does your browser actually bypass it using IPv6 address?

I don't think custom zone file would help you as it can't disable other Google services.

l4k3k3m4n

unread,
Aug 31, 2018, 4:54:09 AM8/31/18
to NxFilter
Yes on clients with dual stack ipv6 and ipv4 the webbrowsers prefer ipv6 and will use the returned google ipv6 address.
And like this safe search will not be used.

Jahastech

unread,
Aug 31, 2018, 5:02:17 AM8/31/18
to NxFilter
OK. We will patch it in 2 weeks.

l4k3k3m4n

unread,
Aug 31, 2018, 5:15:31 AM8/31/18
to NxFilter
Great, thanks!
Cheers!

Jahastech

unread,
Sep 6, 2018, 12:56:03 AM9/6/18
to NxFilter
v4.3.2.3 with the fix has been released.

l4k3k3m4n

unread,
Sep 7, 2018, 4:15:29 AM9/7/18
to NxFilter
Yes it is working fine now, thanks.

l4k3k3m4n

unread,
Sep 7, 2018, 7:15:25 AM9/7/18
to NxFilter
I have to correct myself.
Yes windows clients work fine with ipv6 safe search now.

BUT on android google cannot be resolved at all now.
When I turn off safe search android clients work.

Jahastech

unread,
Sep 7, 2018, 7:08:35 PM9/7/18
to NxFilter
We tested it using dig and nslookup and it works as we expected. On Windows, it works but doesn't work on Android? That's very strange. There's nslookup like app on Android. Try that one.

Jahastech

unread,
Sep 7, 2018, 9:31:58 PM9/7/18
to NxFilter
Yeah, it has a problem with Android. We will roll it back with v4.3.2.4 today. We will try to solve IPv6 problem later then.

l4k3k3m4n

unread,
Sep 10, 2018, 2:12:10 AM9/10/18
to NxFilter
Ok thanks.
Looking for a a working solution :)

Regards

Jahastech

unread,
Sep 12, 2018, 10:34:09 PM9/12/18
to nxfil...@googlegroups.com
Try this one,

It worked with my Android phone.

Jahastech

unread,
Sep 12, 2018, 10:34:59 PM9/12/18
to NxFilter
Sorry, the link should be to v4.3.2.5.

l4k3k3m4n

unread,
Sep 13, 2018, 8:22:12 AM9/13/18
to NxFilter
Yes I can confirm it works on android devices.

Is this a public release? Or do I have to remove it again?

Thanks!

Jahastech

unread,
Sep 13, 2018, 8:36:29 AM9/13/18
to NxFilter
It's the final release. Use it.
Reply all
Reply to author
Forward
0 new messages