topic Re: 'DNS name resolution failure' Reports in router in Full Fibre

'DNS name resolution failure' Reports in router

Billx — Sun, 14 Apr 2024 14:51:24 GMT

My Router has reported the following, as errors, today,

14.04.2024 13:39:33 Error DNS DNS name resolution failure (revboostprocdnadsprod.azureedge.net)

14.04.2024 14:44:59 Error DNS DNS name resolution failure(revboostprocdnadsprod.azureedge.net)

Within those 2 times, there are 68 other reports of the same error.

Now this, will fill my router log file in no time.

I dealt with this topic on 20-06-2023 11:57 PM, in

ROUTER 5464 - 'DNS name resolution failure' error

There was no outcome or resolution.

@KeithFrench suggested that this issue should be given the classification of 'Info' rather the 'Error' within the router software.

I suggested that, that would not solve much, as users still want view all other 'Info', and 'Info' is the least serious of all reports.

So, I make a new suggestion, that, as this issue has no relevance and does not cause any harm, the Devices Team remove this issue completely.

How about that?

Re: 'DNS name resolution failure' Reports in router

KeithFrench — Sun, 14 Apr 2024 15:06:05 GMT

Hi @Billx

Not only did I say that the bug was over the message classification being wrongly set as Error, not Informational, as it should be for these DNS messages, I did also suggest to TalkTalk that a checkbox or similar should be there to enable users to display these messages or not. There is new firmware due out at some point a bit later this year, I have no idea what fixes/changes will be included in it, at the moment.

Re: 'DNS name resolution failure' Reports in router

Billx — Sun, 14 Apr 2024 15:16:39 GMT

Hi @KeithFrench

Did you mean then that it be reclassified as 'Info', and that there be a checkbox, selecting between

1. include all 'Info', including 'DNS name resolution failure'

and

2. include all 'Info', except 'DNS name resolution failure'

If that's what you meant, then that would work.

My suggestion would also work.

Bill

Re: 'DNS name resolution failure' Reports in router

KeithFrench — Sun, 14 Apr 2024 15:21:57 GMT

Yes, that is exactly what I meant. I have never seen a router log failed DNS requests before, it certainly is valid, but does in my opinion require user choice if they want to see them or not. So much depends on the fault condition that you are trying to troubleshoot. If you can't access some website, unless you have some of the diagnostic software that I use, having the DNS entries could be a lifesaver.,

Re: 'DNS name resolution failure' Reports in router

Billx — Sun, 14 Apr 2024 17:21:17 GMT

@KeithFrench

Very good, that we agree on what you meant.

I thought you might have meant to have a checkbox, that allowed all 'Info' entries or disallowed all 'Info' entries.

Well, 'having the DNS entries could be a lifesaver', that hasn't been the case for me.

I looked at all these entries in the past, and none of them had any connection with me.

And as it has proven, they have not had any effect. TalkTalk is not bothered with them. And others have not reported any drastic consequences. Therefore, DNS is doing its job.

But, yes they are a nuisance in the router log.

My suggestion, that TalkTalk completely remove reporting of these events, would suit me fine.

Bill

Re: 'DNS name resolution failure' Reports in router

KeithFrench — Sun, 14 Apr 2024 20:58:32 GMT

Of course, you do have to consider one thing here. The DNS queries that fail are due to one or more of a user's devices visiting websites, which in turn pull in content from other sites & these may have invalid URLs in them. However, to display the whole still requires that device to make numerous DNS queries & it is that device that is the cause of all of these logs.

The other thing that you have to bear in mind, I can report bugs to TalkTalk and can offer suggestions, but it is down to TalkTalk if they want to implement them.

Re: 'DNS name resolution failure' Reports in router

Billx — Mon, 15 Apr 2024 10:39:59 GMT

@KeithFrench

As I said, I have looked at all these names, mentioned in the 'DNS name resolution failure' entries in the log, and I can't tie them to anything I am doing. If these companies write their software the way they do, its not any of my problem. It's up to those companies to do less AI, and deal with it. It would take me 300 years to investigate this myself.

Bill

Re: 'DNS name resolution failure' Reports in router

Billx — Mon, 15 Apr 2024 11:06:25 GMT

Hi All,

My Router reported the following, as errors, yesterday evening and night,

14.04.2024 14:50:01 Error DNS DNS name resolution failure (revboostprocdnadsprod.azureedge.net)

15.04.2024 01:09:26 Error DNS DNS name resolution failure(revboostprocdnadsprod.azureedge.net)

Within those 2 times, there were 670 other entries with the same error.

It nearly filled my whole log file.

I did a factory reset later.

Obviously, this is caused by by some Microsoft software, in one of my few devices,

But there is no way I could investigate this, as there are thousands and thousands of processes and applications that Microsoft is running.

Bill

Re: 'DNS name resolution failure' Reports in router

KeithFrench — Mon, 15 Apr 2024 11:50:02 GMT

I totally agree it is very difficult to tie down.

As I have said before, I have already put this forward as a suggestion (it is not a bug). I it gets implemented or not, is up to TalkTalk to decide.

Re: 'DNS name resolution failure' Reports in router

Billx — Mon, 15 Apr 2024 12:14:54 GMT

Hi All,

Now I've got an interesting one.

My Router reported the following, as errors

15.04.2024 12:51:04 Error DNSDNS name resolution failure (65d51797a924132454a596a1816c5e5b7c54f5387da45fb61a990384c97362e)

This has been repeated 12 times until 15.04.2024 12:57:54.

Now regarding investigating this, I don't even know if this is a website.

I think there's a little bit too much AI going on.

Bill

Re: 'DNS name resolution failure' Reports in router

KeithFrench — Mon, 15 Apr 2024 13:49:01 GMT

Hi @Billx

This is possibly a time when the log is useful. One of your devices has submitted a DNS query for the domain:-

65d51797a924132454a596a1816c5e5b7c54f5387da45fb61a990384c97362e

The DNS server in the router has not been able to resolve this to an IP address & has written this fact to the log.

You are right, it is very strange looking. I would think less about AI and more about malware being present on one of your devices. If I was you, I would do a full system malware scan on each of your devices.

Re: 'DNS name resolution failure' Reports in router

Billx — Mon, 15 Apr 2024 17:20:10 GMT

You can't resolve '65d51797a924132454a596a1816c5e5b7c54f5387da45fb61a990384c97362e' into IP address. It could not be a domain name, unless all the techies have gone berserk. No, I don't think so. My few devices are overprotected already.

Bill

Re: 'DNS name resolution failure' Reports in router

Billx — Mon, 22 Apr 2024 09:48:35 GMT

Hi all,

Since 20.04.2024 16:17:12, less than 2 days ago, the story has continued.

With 80 pages x 20 entries per page, the router log has been filled nearly entirely or say 98% with the following entry:

Error DNS DNS name resolution failure (revboostprocdnadsprod.azureedge.net). That's 1600 attempts.

'revboostprocdnadsprod.azureedge.net' is the same culprit, I reported before.

Bill

Re: 'DNS name resolution failure' Reports in router

KeithFrench — Mon, 22 Apr 2024 10:19:02 GMT

Hi @Billx

The crucial part here is, like it or not, all of these log entries are caused by one or more of your own devices trying to resolve unregistered domains to IP addresses. The fact that they are not resolved, generates an entry in the System Log.

As far as a DNS server is concerned you supply it with a true domain name (such as microsoft.com) or a string of garbage (qwertyashimmbbgfgvg), the server must still try and resolve this to an IP address. Domains are not routable, only IP address can be routed to another IP address.

As I have said before, in addition to the classification bug, I have requested that the developers supply a means for the user to choose if they want to see unresolved DNS requests or not (I'd be the first to stop them on my Sagemcom).

Therefore I don't think there is anything to be gained by you keep updating this thread in the manner that you are doing. I answered this thread ages ago now & that should have been that. So far I have spent ages replying to you on two of your threads this morning which is taking up a lot of my time and please be aware, that as a customer, I am not paid for this work I do at all.

Re: 'DNS name resolution failure' Reports in router

Billx — Mon, 22 Apr 2024 10:38:46 GMT

Any idea how, a mere user, can trace 'revboostprocdnadsprod.azureedge.net' amongst my devices, when there are thousands of Microsoft processes running on each of my devices?

Bill

Re: 'DNS name resolution failure' Reports in router

KeithFrench — Mon, 22 Apr 2024 10:55:09 GMT

What I have done in the past is to install Wireshark on each device that supports this application, take traces & then go through them to find a particular domain. However, this is a very complex way of doing this. There is an application on the nirsoft website that will do this in a more simpler way:-

https://www.nirsoft.net/utils/dns_query_sniffer.html

However, it only runs on Windows.

Re: 'DNS name resolution failure' Reports in router

Billx — Mon, 22 Apr 2024 11:41:54 GMT

Yes, @KeithFrench

You had advised me last year sometime, and I went to https://www.nirsoft.net/utils/dns_query_sniffer.html

And I installed, and it is currently installed. However, there were many things I didn't understand within it, so I have hardly used it.

I opened it just now. And the culprit does appear on it, on my current device.

But I think I'll have to pass for now

Thanks

Bill

Re: 'DNS name resolution failure' Reports in router

KeithFrench — Mon, 22 Apr 2024 14:00:31 GMT

That of course, is only half the battle, you would now need to find out why this is happening.

Re: 'DNS name resolution failure' Reports in router

Billx — Mon, 22 Apr 2024 20:59:52 GMT

In the router log, ~~On the computer,~~ 'revboostprocdnadsprod.azureedge.net' seems to be recorded in batches of 5 within the same second, every 5 minutes.

In dns_query_sniffer, I didn't spot any regularity.

In dns_query_sniffer, under 'Host Name', in just over half of the entries, the names are missing.

Under 'Response Time, a lot of the 'response times' are missing. etc.

Quite a few of the 'Host Names' are related to Microsoft.

A lot of others are related to Google, YouTube

There are other 'Host Names', which I don't recognise, but could be related to Google or Microsoft.

community.talktalk.co.uk is present.

Each entry is marked with a red, yellow, or green indicator, but I can't see the particular significance.

YouTube is appearing, even though I am not currently using it.

On the other hand, only 'revboostprocdnadsprod.azureedge.net' is currently causing havoc in the router log'

That's all. Signing off.

Bill

Re: 'DNS name resolution failure' Reports in router

Billx — Tue, 23 Apr 2024 20:08:19 GMT

Hi all,

Since 22.04.2024 10:30 AM, less than 2 days ago, the story has continued.

A further 1400 entries, with the following detail:

Error DNS DNS name resolution failure (revboostprocdnadsprod.azureedge.net).

Bill