NS watch/blacklist sometimes fails

[tripleee]

What problem has occurred? What issues has it caused?

Domains with a subdomain bypass NS checks (originally, I thought anything with www. before the server name, but it seems to be more complex actually).

Recent example, www.eduauraa.com should trigger watched NS but doesn't. https://metasmoke.erwaysoftware.com/post/352164

What would you like to happen/not happen?

NS watches and blacklists should trigger predictably.

[tripleee]

https://metasmoke.erwaysoftware.com/post/422480

[tripleee]

https://metasmoke.erwaysoftware.com/post/422997 bare IP addresses are blacklisted but still not detected

[tripleee]

Ditto https://metasmoke.erwaysoftware.com/post/422998

[tripleee]

https://metasmoke.erwaysoftware.com/post/425265 crucially

[tripleee]

https://metasmoke.erwaysoftware.com/post/425761

[tripleee]

https://metasmoke.erwaysoftware.com/post/426937

[tripleee]

https://metasmoke.erwaysoftware.com/post/427737

[tripleee]

https://metasmoke.erwaysoftware.com/post/428898

[tripleee]

https://metasmoke.erwaysoftware.com/post/428940

[tripleee]

Blacklisted IP not reported: https://m.erwaysoftware.com/posts/uid/meta/389525

[tripleee]

https://metasmoke.erwaysoftware.com/post/431658 didn't trigger for Brenda+Theo (tutuapp.uno)

[tripleee]

https://metasmoke.erwaysoftware.com/post/463575 weirdly didn't trigger even though both www.nimbleappgenie.com and nimbleappgenie.com resolve to 148.66.136.188 (which has been watched for a long time, but which I am now promoting to blacklisted)

[tripleee]

https://m.erwaysoftware.com/posts/uid/stackoverflow/78074913

[tripleee]

https://metasmoke.erwaysoftware.com/post/476511