Bass grabs you those "extra resolvers" you are missing out on when performing Active DNS enumeration. Add anywhere from 100-6k resolvers to your "resolver.txt"
The last 3 seem like they have their own private nameservers as opposed to using a DNS service so those cases would probably need a different functionality in place to handle them rather than adding new provider txts (adding a new list of nameservers doesn't seem to be the right way to go to cover those edge cases)
For each of these I'll give an example domain and then the provider names. Domain: discordapp.com Providers: cloudflare
Domain: gizmodo.com Providers: awsdns-14, awsdns-13, awsdns-15, public, awsdns-37
Domain: github.com Providers: awsdns-01, awsdns-21, awsdns-32, awsdns-52
Domain: yahoo.com Providers: yahoo
Domain: google.com Providers: google
Domain: qq.com Providers: qq
The last 3 seem like they have their own private nameservers as opposed to using a DNS service so those cases would probably need a different functionality in place to handle them rather than adding new provider txts (adding a new list of nameservers doesn't seem to be the right way to go to cover those edge cases)