----------------------------------------------------------------------------------
@MSGID: 2@dont-email.me> 7a00f740
@REPLY: <gd5iek-c685.ln1@esprimo.zbmc.eu>
b6993cf5
@INTL 3:770/1 3:770/3
@REPLYADDR tnp@invalid.invalid
@REPLYTO 3:770/3.0 UUCP
@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: 50/109 153/757 218/840 840 220/70 221/1 6
360 226/17 100 240/1120
SEEN-BY: 267/800 301/1 113 812 310/31 335/364
341/66 463/68 467/888 633/280
SEEN-BY: 712/848 770/1 3 100 330 340 772/210 220
230 3634/12 5005/49 5019/40
SEEN-BY: 5020/715 848 1042 4441 12000 5030/49 722
1081 1474 5054/8 5058/104
SEEN-BY: 5061/133 5075/128
@PATH: 770/3 1 218/840 221/6 301/1 5020/1042 4441