Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add Comments from our users and friends:

...

  • 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.

...

Comments from our users and friends:

  • Leif, our PL:
    • We would remove all DNS code, and make it correct, on top of C-ares/dns.c, and do appropriate things like letting the resolver code properly get notified on epoll events (not like that crap we have now)
    • we should be able to using thread setting in proxy.config.dns.dedicated_thread, make loadbalance on those threads
  • here is the comments from Martin, our TS-435 reporter:
    • Strict map it's ok In reverse mode, but in forward mode the use of wild card it will be useful to use local country or specific DNS server
      example: dest_domain=lapampa.gov.ar named=x.x.x.y serach_list=lapampa.gov.ar
      dest_domain=*.com.ar named=x.x.x.x
    • Why TS must have two DNS handler? I know only one handler is more complex, however why not use SplitDNS with a default mandatory entry like dest_domain=default named=x.x.x.x
    • I am agree with you, if can not resolve the hostname from the dns server provide by SplitDNS, TS must return error to user, and not fail over other dns resolver.
    • I am agree that TS must refuse to work if none DNS is configured.
  • Vijay, from Yahoo:
    • you should think about separating HostDB from DNS, so that people might just want to use only DNS
    • hostdb will also be used to store 1.1 etc... and how many times we failed to connect to host, but i am thinking about some cleanup where we should have less dependency on hostdb