Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-541 SplitDNS cleanup in project HostDBandDNS
  3. TS-597

when using SplitDNS, the common dns setting is not honored

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.1.4
    • 2.1.5
    • DNS
    • None

    Description

      When using the trunk codes, and setup a splitdns.config without wild cast rule:
      dest_domain=yahoo.com named="68.180.131.16"
      dest_domain=inktomi.com named="68.180.131.16"
      dest_domain=google.com named="8.8.8.8"
      and records:
      CONFIG proxy.config.http.no_dns_just_forward_to_parent INT 0
      CONFIG proxy.config.dns.search_default_domains INT 1
      CONFIG proxy.config.dns.splitDNS.enabled INT 1
      CONFIG proxy.config.dns.max_dns_in_flight INT 2048
      CONFIG proxy.config.dns.url_expansions STRING NULL
      CONFIG proxy.config.dns.round_robin_nameservers INT 0
      CONFIG proxy.config.dns.nameservers STRING 202.106.0.20
      CONFIG proxy.config.dns.resolv_conf STRING NULL
      CONFIG proxy.config.dns.validate_query_name INT 0
      CONFIG proxy.config.diags.debug.tags STRING split.|dns.|hostdb.*

      splitdns will just make the default dns server as 127.0.0.1 regards of the setting from /etc/resolv.conf etc

      [Dec 17 21:11:10.792] Server

      {47027459007840} DEBUG: (dns) DNSHandler::startEvent_sdns: on thread 0
      [Dec 17 21:11:10.792] Server {47027459007840}

      DEBUG: (dns) open_con: opening connection 68.180.131.16:53
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) random port = 51000
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) opening connection 68.180.131.16:53 SUCCEEDED for 0
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) DNSHandler::startEvent_sdns: on thread 0
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) open_con: opening connection 68.180.131.16:53
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) random port = 41996
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) opening connection 68.180.131.16:53 SUCCEEDED for 0
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) DNSHandler::startEvent_sdns: on thread 0
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) open_con: opening connection 8.8.8.8:53
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) random port = 26464
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) opening connection 8.8.8.8:53 SUCCEEDED for 0
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) DNSHandler::startEvent_sdns: on thread 0
      [Dec 17 21:11:10.793] Server {47027459007840}

      WARNING: bad '/etc/resolv.conf': no nameservers given
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) open_con: opening connection 127.0.0.1:0
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) random port = 50728
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) opening connection 127.0.0.1:0 SUCCEEDED for 0
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) DNSHandler::startEvent: on thread 0
      [Dec 17 21:11:10.793] Server

      {47027459007840} WARNING: bad configurations: no nameservers given
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) open_con: opening connection 127.0.0.1:0
      [Dec 17 21:11:10.793] Server

      {47027459007840} DEBUG: (dns) random port = 55442
      [Dec 17 21:11:10.793] Server {47027459007840}

      DEBUG: (dns) opening connection 127.0.0.1:0 SUCCEEDED for 0
      [Dec 17 21:11:11.220] Server

      {47027467839248}

      NOTE: cache enabled

      that is confusing, should be fixed.

      Attachments

        1. TS-597.patch
          15 kB
          Zhao Yongming

        Activity

          People

            zwoop Leif Hedstrom
            zym Zhao Yongming
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: