Re: [dns-operations] contact to jimdo.com
On Tue, Jan 26, 2021 at 01:16:09PM +0100, A. Schulze wrote: > > Try doing some more queries. It's not based on the case of the query. > > > > Looks like a load balancer and different versions of the zone. If > > you query for the SOA you can get two different serial numbers. > > "doing more queries" is not how a reolver work :-/ Of course not, that was just a more accurate explanation of the symptoms, and how you might reproduce the analysis. > Temporary disabling caps for *known* domains is something I could do > in my infrastructure. > It doesn't solve the root cause ... The root cause is a dynamic DNS configuration, possibly with load-balancers, where some of the back-end servers report a different SOA and deny the MX. That's likely all the help you can get on this list, you now need to take this up with the owner/operator of the domain in question. -- Viktor. ___ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations
Re: [dns-operations] contact to jimdo.com
Simon Arlott via dns-operations: Try doing some more queries. It's not based on the case of the query. Looks like a load balancer and different versions of the zone. If you query for the SOA you can get two different serial numbers. Hi Simon, yes, that's an other issue with that nameservers. "doing more queries" is not how a reolver work :-/ Temporary disabling caps for *known* domains is something I could do in my infrastructure. It doesn't solve the root cause ... Andreas ___ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations
Re: [dns-operations] contact to jimdo.com
--- Begin Message --- On 2021-01-26 09:43, A. Schulze wrote: I've an issue resolving MX-Records for domains hosted at [ns11,ns12].jimdo.com The servers answer same questions in different ways: dig @ns11.jimdo.com. MIRISSIMA.DE. MX +norec -> NOERROR, no ANSWER dig @ns11.jimdo.com. mirissima.de. mx +norec -> NOERROR, answer BUT: question for an A-Record are answered no matter upper- or lowercase is used. So my MTA try to deliver messages to the webserver :-/ Try doing some more queries. It's not based on the case of the query. Looks like a load balancer and different versions of the zone. If you query for the SOA you can get two different serial numbers. -- Simon Arlott --- End Message --- ___ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations
[dns-operations] contact to jimdo.com
Hello, I've an issue resolving MX-Records for domains hosted at [ns11,ns12].jimdo.com The servers answer same questions in different ways: dig @ns11.jimdo.com. MIRISSIMA.DE. MX +norec -> NOERROR, no ANSWER dig @ns11.jimdo.com. mirissima.de. mx +norec -> NOERROR, answer BUT: question for an A-Record are answered no matter upper- or lowercase is used. So my MTA try to deliver messages to the webserver :-/ Usually, UNBOUND, the resolver I use, can handle capitalization issues. But here, the resolver have no reason to assume a retry with all lowercase will have an other result. Andreas ___ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations
