One week ago I have added few new A records to existing zone mints.rocks
h37.mints.rocks , resh37.mints.rocks
And now sometimes dns resolves it with empty value
But previous 40 records works well, for example
Domain hosted on name.com, standard name servers used. No custom records, only A. All records created via api
I have recreated records few times. Same problems. Some of new record in domain can be with the problem.
For testing I'm using dnschecker.org , every time new dns servers returns wrong value
few times I got "Domain name not resolved" error on my laptop in browser.
intodns.com show's no error. I have no any ideas how to fix the bug. Name.com support unresponsive
wrong dig result example:
~$ dig h37.mints.rocks ; <<>> DiG 9.16.1-Ubuntu <<>> h37.mints.rocks ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38029 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;h37.mints.rocks. IN A ;; Query time: 56 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Aug 12 22:18:36 CEST 2020 ;; MSG SIZE rcvd: 44