INTL 3:770/1 3:770/3   
   REPLYADDR tnp@invalid.invalid   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  7a00f740   
   REPLY:  b6993cf5   
   PID: SoupGate-Win32 v1.05   
   On 10/04/2024 11:14, Chris Green wrote:   
   > I don't know why your system is trying 162.159.200.123 and not the   
   > alternatives, mine seem to find a working IP OK.  Is your DNS good?   
      
   No, it wasn't and I am not sure why.   
      
   I installed BIND which normally works out of the box.   
      
   Its the usual mess of network manager/systemd all fighting to control   
   something probably.   
      
   Yesterday I was getting connection refused on port 53, using the pi's   
   own IP address in resolv.conf - that is 192.168.0.101   
      
      
   I added a working server on the  network, and it sprang to life but when   
   I tested it with its own address it now seems to work as well.   
      
   I just rebooted it and once again, DNS now works???   
      
      
      
      
      
   --   
   It is the folly of too many to mistake the echo of a London coffee-house   
   for the voice of the kingdom.   
      
   Jonathan Swift   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/220   
   SEEN-BY: 135/225 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1   
   SEEN-BY: 221/6 360 226/17 30 100 227/114 229/110 111 112 113 200 206   
   SEEN-BY: 229/307 317 400 426 428 470 550 616 664 700 240/1120 266/512   
   SEEN-BY: 267/800 282/1038 291/111 292/854 301/1 113 812 310/31 320/219   
   SEEN-BY: 322/757 335/364 341/66 342/200 396/45 460/58 633/280 712/848   
   SEEN-BY: 770/1 3 100 330 340 772/210 220 230 5020/400 1042 5058/104   
   SEEN-BY: 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426