...
- Fix SplitDNS: TS-435. in_progress
- cleanup SplitDNS: keep SplitDNS under DNS only, not mess up with codes in proxy/http2.
- make dns more flex:
- way to passthrough HostDB cache
- easy way to setup Origin Source server IP, maybe something like Hosts.
- need to get a way for DNS and(or) HostDB pluginable, can hooking somewhere.
- cleanup old codes.
...
Questions and confusing:
SplitDNS cleanup:
- Why should we care of the domain/search on SplitDNS server? when you setup an SplitDNS, you should know that the map is for strict map, not for wild map, right? so we should remove all these dumping configs/codes.
- When we put SplitDNS handler all handled by DNSprocesser, we sure should kill the default SplitDNS config, as if all strict map in SplitDNS fails, it must go on with the standard DNS resolver. But when you have a SplitDNS config, and you can not resolve the hostname from the dns server provide by SplitDNS, you should not do fail over to any other dns server.
- What is the hell of 127.0.0.1 in the resolver code? 127.0.0.1 will show up, only when you do not specify any dns server by records.config, nor /etc/resolv.conf, not SplitDNS, nor others. at that time, we should rise up a Fatal message too, or should we just refuse to work?
- if we put all hostname<->nsserver mapping codes in DNS module, there maybe something strange when the current codes put these maps in HostDB too.
...