The domain’s DNS looks iffy to me. I’m not sure what exactly is wrong, but things are way off.
When i do queries, they usually SERVFAIL
a few times and eventually work.
http://dnsviz.net/d/obesity-protocol.com/dnssec/
The delegation from the com.
/net.
nameservers is this:
$ digr obesity-protocol.com. @b.gtld-servers.net
; <<>> DiG 9.10.3-P4-Ubuntu <<>> +norecurse obesity-protocol.com. @b.gtld-servers.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23968
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;obesity-protocol.com. IN A
;; AUTHORITY SECTION:
obesity-protocol.com. 172800 IN NS ns1.starhostdesign.net.
obesity-protocol.com. 172800 IN NS ns2.starhostdesign.net.
;; ADDITIONAL SECTION:
ns1.starhostdesign.net. 172800 IN A 108.178.34.214
ns2.starhostdesign.net. 172800 IN A 181.224.144.9
;; Query time: 0 msec
;; SERVER: 2001:503:231d::2:30#53(2001:503:231d::2:30)
;; WHEN: Fri Feb 17 22:30:13 UTC 2017
;; MSG SIZE rcvd: 135
According to the NS
records in your own zone, the nameservers are these:
$ dig obesity-protocol.com. ns
; <<>> DiG 9.10.3-P4-Ubuntu <<>> obesity-protocol.com. ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51240
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;obesity-protocol.com. IN NS
;; ANSWER SECTION:
obesity-protocol.com. 86399 IN NS ns2.m36.siteground.biz.
obesity-protocol.com. 86399 IN NS ns1.m36.siteground.biz.
;; Query time: 408 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Feb 17 22:30:17 UTC 2017
;; MSG SIZE rcvd: 103
$ mhost ns1.m36.siteground.biz.
ns1.m36.siteground.biz. (unsigned) 7501 A 108.178.34.214
$ mhost ns2.m36.siteground.biz.
ns2.m36.siteground.biz. (unsigned) 14400 A 181.224.144.9
Notice that the IP addresses are the same, but the hostnames are different.
Finally, according to its own zone, the nameserver names i mentioned first have completely different A
records from the com.
glue aliasing SiteGround:
$ mhost ns1.starhostdesign.net.
ns1.starhostdesign.net. (unsigned) 3600 A 216.69.185.52
$ mhost ns2.starhostdesign.net.
ns2.starhostdesign.net. (unsigned) 3599 A 216.69.185.52
And that server does not respond to queries:
$ digr obesity-protocol.com. @216.69.185.52
; <<>> DiG 9.10.3-P4-Ubuntu <<>> +norecurse obesity-protocol.com. @216.69.185.52
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 9098
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;obesity-protocol.com. IN A
;; Query time: 34 msec
;; SERVER: 216.69.185.52#53(216.69.185.52)
;; WHEN: Fri Feb 17 22:37:11 UTC 2017
;; MSG SIZE rcvd: 38
So whether it “works” depends on the details of a specific recursive server’s lookup algorithm, what the order of events is, and precisely how and what it caches.
The reason it works for me after a few retries is that i actually use multiple recursive DNS servers with two different implementations; apparently, one of them happens to accept these issues, and one of them doesn’t.
Anyway, this all needs to be sorted out for your DNS to work reliably.