DNS Director bugging out (even when disabled): nslookup returns NOTIMP

[p1r473]

Hi all, thanks for reading this post.
Im having a weird issue with DNS Director.
Its currently disabled. However, sometimes it gets into a state of bugginess where I cant nslookup on 8.8.8.8, causing my Google Homes, and any machines using 8.8.8.8, to break. The error I get from nslookup is 'NOTIMP'

 nslookup google.com 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   google.com
Address: 10.0.0.1
** server can't find google.com: NOTIMP

Enabling and then re-disabling DNS Director fixes this issue which leads me to believe DNS Director is bugging out even when disabled
This issue happens infrequently, maybe once a week.

 

[dave14305]

That looks more like a WAN down redirect from wanduck. Any messages in the router log around that time?

 

[p1r473]

I dont know what time it started (unsure of timestamp) but I can definitely check next time that happens
Right now, I am still in this bugged out state, but WAN is currently up. My internet seems to be working fine except for unable to nslookup from 8.8.8.8/8.8.4.4/1.1.1.1/1.0.0.1
Should I disable "Enable WAN down browser redirect notice"? Is that what you think is the issue?

I am using dual WAN with a failover, but currently connected to primary

 

[dave14305]

Should I disable "Enable WAN down browser redirect notice"? Is that what you think is the issue?

I think that would tell us something, for sure.

 

[p1r473]

I disabled the "WAN down browser redirect notice" and I can nslookup from 8.8.8.8 again (out of bugged state) - however Im not sure if this fixed it, or if the WAN resets after making a router change
Will post back if problem reoccurs.
Thanks Dave!