-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 14/10/18 18:12, Rick Moen via luv-talk wrote:
Quoting Andrew McGlashan (andrew.mcglashan@affinityvision.com.au): Oh, here we go. Someone just has to justify thin nameservice.
Many would say that about not having a backup MX, but anyway, guess we beg to differ on this one. 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. A laptop continuously testing from the same local network as per the Android phone never, ever gets the public answer :confused: The closest I could get to on this is that the WiFi drops out and reconnects, but then a tool to query DNS on the device doesn't give any answers if I disable WiFi too. Something is interfering with the DNS request, somehow. I first thought it was just a K9 problem, but this happens outside of K9. It /may/ be, but I doubt it, that while the mobile's interface is getting it's IP details via DHCP, it has a temporary address that causes the public answer to be returned. Any ideas on this one? Thanks A. -----BEGIN PGP SIGNATURE----- iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCW8LwWQAKCRCoFmvLt+/i +9wvAP42n5jHv+GFLwdUqP6sLaC7r6O3YCJZS0VxjHYL3eMpiwEAtS/DR3Cj7P3i 3ymK9BrTEDK5Uh3T6tKZlDsi8Pf8UqI= =YfTQ -----END PGP SIGNATURE-----