SERVFAIL on local dig, but it works out on the internet

I can't seem to get a DNS resolution on my local machine to qwikboard.io.

Locally (MACOS Catalina):
BlahBlahBlah ~Fri Feb 2610:31:07:->$nslookup qwikboard.io
;; Got SERVFAIL reply from 192.168.0.1, trying next server
Server: 205.171.3.65
Address: 205.171.3.65#53

** server can't find qwikboard.io: SERVFAIL

BlahBlahBlah ~Fri Feb 2610:31:20:->$

Dig w/ Trace: seems to find it
BlahBlahBlah ~Fri Feb 2610:31:20:->$dig qwikboard.io +trace

; <<>> DiG 9.10.6 <<>> qwikboard.io +trace
;; global options: +cmd
. 190303 IN NS g.root-servers.net.
. 190303 IN NS k.root-servers.net.
. 190303 IN NS j.root-servers.net.
. 190303 IN NS a.root-servers.net.
. 190303 IN NS m.root-servers.net.
. 190303 IN NS h.root-servers.net.
. 190303 IN NS b.root-servers.net.
. 190303 IN NS i.root-servers.net.
. 190303 IN NS c.root-servers.net.
. 190303 IN NS e.root-servers.net.
. 190303 IN NS f.root-servers.net.
. 190303 IN NS l.root-servers.net.
. 190303 IN NS d.root-servers.net.
. 190303 IN RRSIG NS 8 0 518400 20210307210000 20210222200000 42351 . VS1wQt2svtr5VYEPZdHfbh5v1/Wwutrrzt/c/CI3FtUuBeKipacdaYTe FQ9WOyvP8o4b0nwbuxhFvV7dtK4rAQfR0BkPG_KQSxvmnuF7K0CxPlx4 yHuuhER2hHqXUyWKXI59Fbh0sD8J0DBfEc5zkeLPcFzuv95mZy63O5NI QrNvCVLYOUghJBFw317Bjr1XutzhmmisnhkqD9XtBFr1a5w5/Qz6uZjL ugH5b0zEaMoqD3kiMPOw5SSx1ElUS2Bw_Xas6lt1a7g1j90Sih0gvBgt m/uca4kANBk0hzSt6XZjNrAGhx9wm/yuPHZCqjz8MtTI7ECBmjzdU8+G rZ9O8g==
;; Received 525 bytes from 192.168.0.1#53(192.168.0.1) in 9 ms

io. 172800 IN NS b0.nic.io.
io. 172800 IN NS c0.nic.io.
io. 172800 IN NS a2.nic.io.
io. 172800 IN NS a0.nic.io.
io. 86400 IN DS 57355 8 2 95A57C3BAB7849DBCDDF7C72ADA71A88146B141110318CA5BE672057 E865C3E2
io. 86400 IN RRSIG DS 8 1 86400 20210311170000 20210226160000 42351 . O/sJsMi/b0LdBtCrknBgtOQ1I1fRV8qGTteVDH9_KLCY_I7d80u7uZsT J1Jb47_fwNNxSc4CMRC4aI2SFeaLzwaT7mknjT5ChFVleu18VGEmilRF HUoheFn_y45uP3ouYgdpMDnRy8lLnd_tPGPBTAyMJ1pigLzzFmnddyuG H3uQiZ6U1PKG1EPazyCaYuooiCTaH_occWhXUjnV5AiOj/MCpNfaWyTW 6w8PIz9X7QH_i5whC9AvkKjdVmVsvOTUoKm_r1XG0_L88eHUh8dNJI_o h7hdQSaW4j0YiM5aKR+vr5cxoRBNKo6EKdaSotxiDExSgXM4Z4XM29Yr pABeeA==
;; Received 624 bytes from 192.33.4.12#53(c.root-servers.net) in 38 ms

qwikboard.io. 86400 IN NS ns-182.awsdns-22.com.
qwikboard.io. 86400 IN NS ns-1692.awsdns-19.co.uk.
qwikboard.io. 86400 IN NS ns-1217.awsdns-24.org.
qwikboard.io. 86400 IN NS ns-848.awsdns-42.net.
u92tce82j4l1t382opcath2ulsjsm9qg.io. 900 IN NSEC3 1 1 100 332539EE7F95C32A U931DDLVCQOE3B8VQ9VT7RJOK0DILU6V NS SOA RRSIG DNSKEY NSEC3PARAM
u92tce82j4l1t382opcath2ulsjsm9qg.io. 900 IN RRSIG NSEC3 8 2 900 20210319173034 20210226163034 33828 io. TReR5Civi8kJanQniAGhaSazEUZCVsG72gcIxEMUPuwxWQ2sj1hbLgdJ etc_CVD5oVcUaDid04d7DGdDcrXGfGF_X5dAWI0i7uO/EwVembXciGUu MoCZbSQRP3mevbYtF5sDZ56/RfLo9XY1ZgMri6JZWnNllptKRgzzmDbV CH8=
ppvtf3n9e78tui6b0aoardqjmg26mjk9.io. 900 IN NSEC3 1 1 100 332539EE7F95C32A PQ0NI0MV5FETPGP9I14ECRR18OITKB9N NS DS RRSIG
ppvtf3n9e78tui6b0aoardqjmg26mjk9.io. 900 IN RRSIG NSEC3 8 2 900 20210318151645 20210225141645 33828 io. JFVx/x8q2aZp_cNLKjBZRv47jMycrQCgGLphub2Bgl9sqDTKGD67U_33 rTzcvAKPOulCObBNKI6uyBbcFFCrXaCR57DeEjC7NOIhII1VMQcXqSjC IoIae0wa5WtKSz3SFpkaNVxlhwPWj76fvY58jfOgoG0lEtrhX9fncw4u Y4I=
;; Received 680 bytes from 65.22.160.17#53(a0.nic.io) in 50 ms

qwikboard.io. 60 IN A 18.216.17.91
qwikboard.io. 172800 IN NS ns-1217.awsdns-24.org.
qwikboard.io. 172800 IN NS ns-1692.awsdns-19.co.uk.
qwikboard.io. 172800 IN NS ns-182.awsdns-22.com.
qwikboard.io. 172800 IN NS ns-848.awsdns-42.net.
;; Received 197 bytes from 205.251.196.193#53(ns-1217.awsdns-24.org) in 20 ms

BlahBlahBlah ~Fri Feb 2610:32:24:->$

An EC2 instance, in a completely different AWS account can dig and ping it:
ubuntu@ip-10-1-1-119:$ ping qwikboard.io
PING qwikboard.io (18.216.17.91) 56(84) bytes of data.
64 bytes from ec2-18-216-17-91.us-east-2.compute.amazonaws.com (18.216.17.91): icmp_seq=1 ttl=29 time=12.0 ms
64 bytes from ec2-18-216-17-91.us-east-2.compute.amazonaws.com (18.216.17.91): icmp_seq=2 ttl=29 time=12.1 ms
64 bytes from ec2-18-216-17-91.us-east-2.compute.amazonaws.com (18.216.17.91): icmp_seq=3 ttl=29 time=12.6 ms
^C
--- qwikboard.io ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 12.051/12.285/12.686/0.311 ms
ubuntu@ip-10-1-1-119:$ dig qwikboard.io

; <<>> DiG 9.11.3-1ubuntu1.14-Ubuntu <<>> qwikboard.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17266
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;qwikboard.io. IN A

;; ANSWER SECTION:
qwikboard.io. 60 IN A 18.216.17.91

;; Query time: 31 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Fri Feb 26 17:33:15 UTC 2021
;; MSG SIZE rcvd: 57

ubuntu@ip-10-1-1-119:~$

What is going on ?

I'm finding Route53 to be highly unavailable (usability < 0)...

Please advise...