[
https://issues.apache.org/jira/browse/TS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Giedymin updated TS-313:
------------------------------
Attachment: TS-313-Interim.patch
Interim Patch, Need somewhere to put this where I won't lose whatever I did
thus far.
This patch is not complete.
> DNS and resolvers improvements
> ------------------------------
>
> Key: TS-313
> URL: https://issues.apache.org/jira/browse/TS-313
> Project: Traffic Server
> Issue Type: Improvement
> Reporter: Miles Libbey
> Priority: Minor
> Attachments: TS-313-Interim.patch
>
>
> (was yahoo bug 1542263)
> Original description
> by Leif Hedstrom 2 years ago at 2007-10-16 17:00
> There are two options to configure/manage how TS finds resolvers via
> records.config:
> CONFIG proxy.config.dns.round_robin_nameservers INT 0
> CONFIG proxy.config.dns.nameservers STRING NULL
> Without these set, TS will simply "parse" /etc/resolv.conf, to find
> nameserver/resolver entries. This is
> fine. However, there are a few things that are "broken" or could be improved
> with the two options above:
> 1) If you want to do "round robin" over your resolvers, you must also
> explicitly define the set of servers in
> the dns.nameservers config. There is no way to have it round robin over the
> default resolvers from /etc/resolv.conf.
> 2) You can not set an explicit set of dns.nameservers, without also making
> them be used in a round robin fashion. This
> is highly undesirable for instance if you want to use a local resolver first
> (listening on 127.0.0.1), but fall
> back to a set of regular resolvers.
> 3) Once listing explicit dns.nameservers, there is no way to have it also add
> the implicit resolvers from
> /etc/resolv.conf. It'd be very useful if you could "include" an external
> filename as part of the nameservers
> list, e.g.
> "127.0.0.1,/etc/resolv.conf"
> I'd suggest we separate the intertwined relationship between the two options,
> which would solve issues #1 and #2. As a
> bonus feature, we should be able to either implement the flexibility of #3,
> or at least make it possible (via a new
> config option) to include /etc/resolv.conf resolvers even when
> dns.nameservers is set.
> Marking this as an RFE, as it's not exactly a bug, but it's still somewhat
> critical for us to support this properly.
>
> Comment 1
> by Yung-Zen Lai 21 months ago at 2008-07-09 18:56:24
> Per issue #2, "proxy.config.dns.nameservers" config currently only works
> while setting "CONFIG
> proxy.config.dns.round_robin_nameservers INT 1". Even only one
> dns.nameservers is set. It seems not that make
> sense. ^^a
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
