DNS issues

[#1]

Just wondering if anyone else is seeing the same as us on our home connection (using standard PlusNet DNS servers). Basically the domain click.pstmrk.it can't be resolved. Swapping to Google DNS servers (8.8.8.8), or Cloudflare (1.1.1.1) and everything works fine?

Using PlusNet DNS - broken:

$ dig @212.159.13.49 click.pstmrk.it

; <<>> DiG 9.10.6 <<>> @212.159.13.49 click.pstmrk.it
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59115
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;click.pstmrk.it.               IN      A

Using Google DNS - works as expected:

$ dig @8.8.8.8 click.pstmrk.it

; <<>> DiG 9.10.6 <<>> @8.8.8.8 click.pstmrk.it
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26505
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;click.pstmrk.it.               IN      A

;; ANSWER SECTION:
click.pstmrk.it.        60      IN      A       52.18.252.197
click.pstmrk.it.        60      IN      A       34.249.186.140
click.pstmrk.it.        60      IN      A       52.210.116.177

[#2]

Not so much as the DNS being broken as it simply not resolving that address, possibly due to propagation delay.

@dave 

This DOES resolve via the IPv6 DNS so it looks to be confined to IPv4 DNS service.

I can see the issue as afar out as - 81.134.101.161 [BT-UK-AS BTnet UK Regional network]

[#3]

Thanks for confirming it's not just me