NetSurf sluggish on ARMX6

I have NetSurf running on three machines. A Pi4 a Pi3 and an ARMX6.
AFAICT NetSurf Choices are the same on all machines., all of which are running 5.29.
The NetSurf version are all recent, though I do not think this is relevant as the problem has existed over several changes of version.
All three have Home page set to: the following:
https://rickman.orpheusweb.co.uk/lynx/
and are set to open the NetSurf window on startup.
(the homepage is very small it is a simple html page containng some weblinks.

On the two Pis the window opens and the contents appear instantly.
On the ARMX6 the window opens and there is a delay of 15 seconds before the window is populated.
Any idea as to what may be cauisng this.

On the ARMX6 the window opens and there is a delay of 15 seconds

The delay seems to be caused by NetSurf timing out because it is using an out of date primary name server.
This is from the NetSurf log file:-

(0.240000) [INFO netsurf] frontends/riscos/gui.c:1107 ro_gui_check_resolvers: 
Inet$Resolvers ': 192.168.1.55 212.104.130.9'

If it’s Inet$Resolvers, wouldn’t your Network settings be the place to look?

If it’s Inet$Resolvers, wouldn’t your Network settings be the place to look?

Yes absolutely, but I have examined every option in NetWork Settings. There is no sign of 192.168.1.55 anywhere. It was hard coded in the Hosts window but I erased it a week ago. Nonetheless NetSurf is still using it. I am supposing that the Internet stack has some sort of persistent cache which NetSurf is picking up.

I’m not at the Pi, sitting out in the sun with a tea (again!).

Edited… It bugged me. I’m looking at my machine.

Hard to see the screen with sunglasses. ;)

Okay, look at the files in $.!Boot.Choices.Internet, specifically Startup.
See if the address is still mentioned there.

There is no sign of ..1.55 in Configuration Network.

What’s your primary DNS now? And have you rebooted since changing these things?

which NetSurf is picking up

As far as I’m aware, Netsurf doesn’t deal with any of that low level stuff, it just asks the Resolver to look up an address.

If you go to the command line and enter ping heyrick.eu does it also take a while to get started?

Thanks – I have found an obey file in PreDesk
SCSI::SSD.$.!BOOT.Choices.Boot.PreDesk.SetupNet
This contains one line:
Run BootResources:!Internet
Looking inside !Internet there is no sign of the errant DNS id.
I will keep looking!

If you go to the command line and enter ping heyrick.eu

Instantaneous.

will keep looking!

Case closed (red face emoji)
I found a two year old obey file that was setting Inet$Resolvers to point to PiHole. This was intended to be a temporary measure while testing. I forgot to remove it when I pointed the router at PiHole. This was not a problem all the time the PiHole server was working but its SD card was destroyed by a power cut two weeks ago and NetSurf has been routed through a non-existent DNS server ever since.

Ah, the joy of temporary “I’ll just put this here” stuff. I’m sure we’ve all been there, done that, and subsequently misplaced the t-shirt. ;)

Glad you got it sorted.

Ah, the joy of temporary “I’ll just put this here” stuff.

I get asked for temporary solutions at work.¹
When I’m being polite the answer is No, not happening. Otherwise, well, the second word is “off”

¹ Someone in the dept. once introduced a set of mini-switches hanging off the low number of points back to proper switches “temporarily, until the new datapoints are installed” – 10 f’n years…
The last one removed was presented to me along with a lump hammer :)

I forgot to remove it when I pointed the router at PiHole.

DHCP: DNS and gateway settings