
Unfortunetely it's not reachable:
me@machine:~ $ nslookup mydomain.pl ns-cloud-c1.googledomains.com
Server: ns-cloud-c1.googledomains.com
Address: 216.239.32.108#53
** server can't find mydomain.pl: REFUSEDYou seem to be migrating your domain name from a different provider to Google Cloud DNS. If that is the case (it's also applies for new configuration also), you need to update the NS records of your registrar with the NS records you currently have in Cloud DNS. This official documentation [1] might come in handy in your case. I would suggest you to use the dig command (or nslookup) to confirm the DNS configuration you provided is indeed active in your domain registrar. If you find that those NS records are not properly updated, I recommend you to go to your registrar management interface and update the name servers of your domain name with the NS records indicated in the the Cloud DNS public zone.
The output of the following dig command should list the same name servers you declared in your zone configuration file. For example:
dig NS mydomain.pl +short
ns-cloud-*1.googledomains.com.
ns-cloud-*2.googledomains.com.
ns-cloud-*3.googledomains.com.
ns-cloud-*4.googledomains.com.
“*” can be a,b,c and d, you would have to confirm it from you CLoud DNS Zone details.
However, it is showing the following:
dig NS mydomain.pl +short
If mydomain.pl is your actual domain, its NS records do not seem to be updated.
Keep in mind that the full propagation of your configuration changes might take up to 48 hours and during that time frame some locations might receive the right answers while others might not.
Once the propagation is completed you should be able to resolve any queries related to your domain provided that the target records (A, MX, etc.) are already created.