You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/08/25 05:18:17 UTC

[jira] Assigned: (TS-422) DNS proxy?

     [ https://issues.apache.org/jira/browse/TS-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom reassigned TS-422:
--------------------------------

    Assignee: Leif Hedstrom

> DNS proxy?
> ----------
>
>                 Key: TS-422
>                 URL: https://issues.apache.org/jira/browse/TS-422
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>            Priority: Minor
>             Fix For: 2.1.3
>
>
> Do we still need to support DNS proxying? It is disabled by default, via:
>  {CONFIG, "proxy.config.dns.proxy.enabled", "", INK_INT, "0", RU_RESTART_TM, RR_NULL, RC_INT, "[0-1]", RA_NULL}
>   {CONFIG, "proxy.config.dns.proxy_port", "", INK_INT, "53", RU_RESTART_TM, RR_NULL, RC_INT, "[0-65535]", RA_NULL}
> but there is also a #define at build time (DNS_PROXY) to completely disable it. I'm tempted to say that we ought to remove it entirely. Getting rid of it would eliminate a bunch of code, potentially allowing us to simplify a lot of code (particularly in the future, if/when we switch to something like c-ares).
> Thoughts?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.