You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this feature is planned, you might want to cache forward DNS lookups and use that data instead of relying on the PTR records, as the latter doesn't always provide helpful information:
$ host www.google.com
www.google.com has address 74.125.225.146
www.google.com has address 74.125.225.147
www.google.com has address 74.125.225.148
www.google.com has address 74.125.225.144
www.google.com has address 74.125.225.145
www.google.com has IPv6 address 2607:f8b0:4009:805::1014
$ host 74.125.225.146
146.225.125.74.in-addr.arpa domain name pointer ord08s09-in-f18.1e100.net.
Doing a bunch of reverse lookups at once could take a long time and make the user interface unresponsive. Parallelizing the requests and/or displaying partial results may help.
Also, beware of malicious DNS servers returning unexpected content in the hostname field:
Would make it easier to judge what apps are doing.
The text was updated successfully, but these errors were encountered: