Disable SRTT and enable round-robin for forwarders

I have a question about how smooth round-trip-time (srtt) works. If I declare 5 separate DNS servers to forward queries to and one of them is much faster than the other one, naturally the bulk of all queries will go towards that host because of its low curve, correct? However, what happens when th

Reference to statistics-channels output?

Is there a reference to what the entries in the statistics-channels output mean? Specifically I'm interested in the memory contexts section which contains multiple entries named "cache", but I have no way to map what view that cache statistic is referencing; for example: 0x

Re: spf ent txt records.

>It is or would have been, very little cost to publish SPF records. Not until we fix the provisioning problem. (News flash: in 99.9% of the Internet, people do not edit master files with vi.) In the early days of SPF, it was remarkably hard to get TXT records provisioned, even though TXT records

Re: spf ent txt records.

>I've not been keeping up with the IETF; is there a document that >describes what looks like a de facto standard of using _pname labels >with TXT RRs that is being followed by at least DMARC and DANE in >*._tcp.example.com, *._smimecert.example.com, and _dmarc.example.com No, but Dave Crocker is w

Re: spf ent txt records.

> From: John Wobus > 1) An RFC (or RFCs) that specifies a set of specific TXT record content > formats that are specified to have particular meanings, e.g. 'don't do > the > following unless it's an SPF record'. I've not been keeping up with the IETF; is there a document that describes what lo

Re: spf ent txt records.

On Mar 18, 2013, at 12:00 AM, Mark Andrews wrote: It's not that is is esthetically pleasing to put SPF data into its own RR type. It's that TXT has been hijacked and contining to add more uses to TXT does not scale. TXT is a reasonable record for proof of concept. It isn't and never has been a

Re: Dig for link-local

Transport has nothing to do with content in DNS. If your client asks for an record it will get the appropriate answer according to the zone's records (a value or an error condition) regardless on whether the query was made over IPv6 or IPv4. That said, you can 'hack' around this expected beha

Re: Dig for link-local

Hello, On Mar 22, 2013, at 12:13 PM, Kevin Darcy wrote: > I'm not sure what you're asking, exactly. Are you surprised that named would > respond on an IPv6 link-local address if configured with "listen-on-v6 { any; > };"? Can an ipv4-only server give an ipv6 address as part of an overall ans

Re: Dig for link-local

link-locals are not that special, with the exception of the % decorator... other than that, they work exactly like any other address. Bind/Apache/ will listen on link locals and they can be used as route next-hops too. regards, ~Carlos On 3/22/13 1:13 PM, Kevin Darcy wrote: > I'm not sure what

Re: Dig for link-local

I'm not sure what you're asking, exactly. Are you surprised that named would respond on an IPv6 link-local address if configured with "listen-on-v6 { any; };"? - Kevin On 3/22/2013 5:35 AM, Alok Raj wrote: Hi, How dig-command is able to resolve an ip using link-local address, /etc/r

Dig for link-local

Hi, How dig-command is able to resolve an ip using link-local address, /etc/resolv.conf has only one entry - ipv6-link link local address, if I write dig www.domain.com, it is able to resolve that and print the address. Can anyone help me out in documentation or code ple