Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Use a larger buffer than the default, so that more queries will succeed #361

Merged
merged 4 commits into from
Feb 4, 2015

Conversation

bboreham
Copy link
Contributor

Addresses #360. A complete fix would involve implementing TCP fallback, but raising the limit from 512 bytes to 1400 should accommodate a large fraction of real-world responses.

The 'unit' test makes the assumption that type ANY on cisco.com will give a large response. Empirically you also have to add the EDNS0 record in order to get a long response - experiment with commands like dig ANY cisco.com. +qr +noedns

@rade
Copy link
Member

rade commented Jan 23, 2015

This is intended to fix #360, right?

Presumably we should open a separate issue to implement TCP fallback?

@bboreham
Copy link
Contributor Author

Edited description and added #362.

@@ -77,6 +78,15 @@ func TestDNSServer(t *testing.T) {
if !(len(r.Answer) > 0) {
t.Fatal("Number of answers > 0")
}
// Now ask a query that we expect to return a lot of data.
m.SetQuestion("cisco.com.", dns.TypeANY)
m.SetEdns0(UDPBufSize, false) // Special magic to coax the other end into complying

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

@rade
Copy link
Member

rade commented Feb 1, 2015

@bboreham what is happening with this?

@squaremo squaremo merged commit 04a7aa1 into weaveworks:master Feb 4, 2015
@rade rade modified the milestone: 0.10.0 Apr 18, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants