Netalyzr report - in yellow-how to resolve this

[jraju]

The resolver at 208.67.222.222 could not process the following tested types: •Medium (~1300B) TXT records
Requests from this resolver come from 67.215.80.21. This resolver requires 358 ms to fetch a result from our server and 310 ms to return a result from its cache. It does not validate DNSSEC. It does not provide requested DNSSEC records. It does not wildcard NXDOMAIN errors.
The resolver at 208.67.220.220 could not process the following tested types: •Large (~3000B) TXT records
Requests from this resolver come from 67.215.80.15. This resolver requires 322 ms to fetch a result from our server and 309 ms to return a result from its cache. It does not validate DNSSEC. It does not provide requested DNSSEC records. It does not wildcard NXDOMAIN errors.
                           how to resolve this?

[Boggin]

I changed my wireless adapter to OpenDNS and ran Netalyzr which said it could process all tested types, so don't know why it couldn't for you.

Direct probing of DNS resolvers (?) –

Your system is configured to use 4 DNS resolver(s).

The resolver at 208.67.222.222 can process all tested types. Requests from this resolver come from 208.69.34.13. This resolver requires 188 ms to fetch a result from our server and 121 ms to return a result from its cache. It does not validate DNSSEC. It does not provide requested DNSSEC records. It does not wildcard NXDOMAIN errors.

The resolver at 208.67.220.220 can process all tested types. Requests from this resolver come from 208.69.34.13. This resolver requires 182 ms to fetch a result from our server and 167 ms to return a result from its cache. It does not validate DNSSEC. It does not provide requested DNSSEC records. It does not wildcard NXDOMAIN errors.

The resolver at 8.8.8.8 can process all tested types. Requests from this resolver come from 74.125.73.76. This resolver requires 343 ms to fetch a result from our server and 366 ms to return a result from its cache. It validates DNSSEC. It provides DNSSEC records upon request. It does not wildcard NXDOMAIN errors.

The resolver at 8.8.4.4 can process all tested types. Requests from this resolver come from 74.125.73.71. This resolver requires 419 ms to fetch a result from our server and 254 ms to return a result from its cache. It validates DNSSEC. It provides DNSSEC records upon request. It does not wildcard NXDOMAIN errors.

The reference to Google's 8.8.8.8 / 8.8.4.4 is for my LAN which I didn't change for the analysis, but change your TCP/IPv4 Properties to auto DNS then to Google's, running Netalyzr for each to compare.

[jraju]

Hi, Boggins. come here after 3 days of no internet access.
                             If i set that to auto, then it takes the router, which is giving more trouble, that netalyzr list some amazon.com.
                             I want to know, what it says in my log.

[Boggin]

Was the disconnect ISP related ?

I've already said that I don't know why OpenDNS could not process the tested types and I don't understand your last post regarding the router or Amazon.com

Do you still get the same Netalyzr report when using auto DNS and/or Google's DNS ?

[jraju]

Hi, boggins , yes. When i use the ISP dns, then it gives the amazon.com results.

[Boggin]

That's the bit I don't understand - what Amazon results ?

[jraju]

Hi, when i checked with those settings, it says it redirects in to amazon.com. So, i have chosen the google dns and tried the check again. It gives me the same results, as i have enclosed.

[Boggin]

Run this MS Fixit to reset the Hosts File then try it again. https://support.microsoft.com/en-gb/kb/972034

Scroll down for the Win 7 button.

[jraju]

I have done as you said. I enclose the problematic entries as rose alerts.
The result after running the fixit, is as follows:
The resolver at 208.67.222.222 can process all tested types. Requests from this resolver come from 67.215.80.13. This resolver requires 472 ms to fetch a result from our server and 456 ms to return a result from its cache. It does not validate DNSSEC. It does not provide requested DNSSEC records. It does not wildcard NXDOMAIN errors.

The resolver at 208.67.220.220 can process all tested types. Requests from this resolver come from 67.215.80.17. This resolver requires 469 ms to fetch a result from our server and 435 ms to return a result from its cache. It does not validate DNSSEC. It does not provide requested DNSSEC records. It does not wildcard NXDOMAIN errors.
Hi, boggins, now it seems the test is ok or not. pl confirm. How, what would have been the possible reason . Is there any change from previous logs

[jraju]

Hi, the yellow alert:
Your DNS resolver is unable to receive a medium sized (~1400 byte) DNS response successfully, even though it advertises itself as EDNS-enabled.

Your DNS resolver is unable to receive a large (>1500 byte) DNS response successfully, even though it advertises itself as EDNS-enabled.
update: i have disabled ping in the wan settings of the router. Would this be the cause? Because, if i enable ping, then grc.com denotes as ping test failed. To safeguard , i did this. ple

[Boggin]

Because your DNS was being redirected.

I don't know what caused that but it can be from what is known as a Google Redirect infection and it alters the Hosts file.

Run AdwCleaner - https://toolslib.net/downloads/viewdownload/1-adwcleaner/ and then do a scan with the free version of MBAM which I think you have installed.

MBAM has settings to treat PuPs and PuMs as malware and that is activated through Settings/Detection and Protection and using the dropdowns to change to those.

Regarding your last post, I think I get something like that and it relates to the MTU which is a max of 1500 less the overhead of 28, but I'd have to run Netalyzr again to confirm, although that bit about EDNS doesn't ring a bell.

[jraju]

Hi, I will do the test, by adw cle, mbam. But I am doing it them regularly .
 Please see this as well
Netalyzr detected the following proxies:
◦Port: 25 , Response Time: 2 ms
◦Port: 110 (POP3), Response Time: 2 ms
◦Port: 143 (IMAP), Response Time: 2 ms
◦Port: 465 (SMTP/SSL), Response Time: 3 ms
◦Port: 587 (Authenticated SMTP), Response Time: 0 ms
◦Port: 993 (IMAP/SSL), Response Time: 0 ms
◦Port: 995 (POP/SSL), Response Time: 8 ms
                     Please say what it denotes and how to resolve

[Boggin]

I don't have any Proxies - it must be the way your ISP has set their router up, so you'll need to take that up with them.

Just Google those items for what they are.

[jraju]

Hi, I remember now.
               I have enabled imap and pop3 settings in gmail , to get all the mails addressed to my yahoo.co.in account. Would that anything with router?
               Or is it some other thing?
                    I enabled years back and now getting all yahoo mails to my gmail

[Boggin]

That will be it - as you hadn't mentioned about setting anything up, I assumed it was an ISP router setting.

If you still have MiniToolBox, run that and see what that says about any Proxies.