On Tue, 15 Jan 2019, factoreal wrote:
> Very thanks for your response, about issues in keeping up-to-date, in
> recent days there are some major problem in DC and will be resolved in
> days.
> I know we are in the secondary list, I meant why aren’t we included in
> the primary list anymore.
No idea. The masterlist had a weird type for your mirror. I changed that now,
maybe that was it.
> And about the our DNS, I think there is no problem, can you please
> tell me the exact problem? You can check our DNS health
> here: https://intodns.com/asis.io
| asis.io zone: The server(s) were not responsive to queries over UDP. (198.211.118.83)
| asis.io/DNSKEY (alg 7, id 11361): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. (94.232.173.136, UDP_0_EDNS0_32768_4096)
| asis.io/DNSKEY (alg 7, id 23774): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. (94.232.173.136, UDP_0_EDNS0_32768_4096)
| debian.asis.io/A: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. (94.232.173.136, UDP_0_EDNS0_32768_4096)
| io to asis.io: The glue address(es) for dns5.asis.io (198.211.118.83) differed from its authoritative address(es) (76.74.170.21).
via dnsviz.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `- https://www.debian.org/