-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, On 14/10/18 18:46, Rick Moen via luv-talk wrote:
Quoting Andrew McGlashan (andrew.mcglashan@affinityvision.com.au): IMO, that's rather a bit more urgent and severe a breakdown than if incoming SMTP deliveries are merely stuck in a 4-day holding pattern pending your standing up a new MTA host.
I'm not positive, but I think if mail is in the queue and resolution for the domain name isn't forthcoming due to possible down DNS server(s), then the mail will stay in the queue and it will be tried for delivery later with fresh DNS requests as well (in terms of mail when it comes to DNS answers). Of course, finding a server for other services (web for instance) would be an immediate problem when the TTL expires.
I do have a DNS problem that is bugging me.....
Android phone, mobile data off, local WiFi on. Sometimes the mobile gets DNS answers for public DNS instead of the private one... running bind9.
Using views, I guess?
yes.
A laptop continuously testing from the same local network as per the Android phone never, ever gets the public answer :confused:
Yeah, don't know offhand. Maybe closely check the BIND9 logs for clues about why some queries are being handed the wrong view data? Double-check the Android 'phone about what network it's on when this happens. (I'm handwaving, there, out of lack of knowledge about what to check on such a smartphone.)
Any ideas on this one?
Wish I did. It's peculiar, all right.
Wish you did too ;-) Cheers A. -----BEGIN PGP SIGNATURE----- iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCW8L2gwAKCRCoFmvLt+/i +wL1AP0WnB0KUJCtmdBV33835L3N8WMos7gzEXACbWwz179KKAEAg2WtclYKcszy jh5MFJHA64PSTTvMTOWfdFNmUKOZ6ak= =089F -----END PGP SIGNATURE-----