On Sat, Sep 17, 2022 at 11:54:57AM +0200, Matus UHLAR - fantomas wrote:
> your domain is registered to ns1.netregistry.net. nameservers:
>
> Name Server: NS1.NETREGISTRY.NET
> Name Server: NS2.NETREGISTRY.NET
> Name Server: NS3.NETREGISTRY.NET
>
> however, NS records say otherwise:
>
> sbt.net.au. 3600 IN NS ns1.yourdnshost.net.
> sbt.net.au. 3600 IN NS ns2.yourdnshost.net.
> sbt.net.au. 3600 IN NS ns3.yourdnshost.net.
>
> these servers have the same IP addresses, but such discrepancy can cause you
> troubles.
1. Google DNS is *parent-centric*. What matters are the NS records
published by .net.au, presently (perhaps changed recently):
sbt.net.au. NS ns1.partnerconsole.net.
sbt.net.au. NS ns2.partnerconsole.net.
sbt.net.au. NS ns3.partnerconsole.net.
> currently 8.8.8.8 (and 1.1.1.1) fail to return response for your domain:
>
> % dig mx sbt.net.au @8.8.8.8
If this domain was in fact served by netregistry.net, that could well
have been the problem. There is an ongoing over 24hour DNS outage at
netregistry.net (where, e.g., they seem to be dropping all DNS queries
from most Google DNS resolvers).
https://status.webcentral.au/
So any domains (mostly Australian) served by netregistry.net (directly,
or indirectly, when e.g. the A records of nameservers for a domain are
in turn served by netregistry, ...) fail to resolve from Google's
perspective.
--
Viktor.
