starred/geodns
1
0
Fork 0
mirror of https://github.com/abh/geodns.git synced 2026-04-26 19:35:51 +03:00
Code Issues 151 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #143] Long text does not work #385

New issue
Open
opened 2026-03-13 14:49:54 +03:00 by kerem · 4 comments
kerem commented 2026-03-13 14:49:54 +03:00
Owner
Copy link

Originally created by @ghost on GitHub (May 3, 2024).
Original GitHub issue: https://github.com/abh/geodns/issues/143

Hello there,

I found out that querying txt with long results will not work on this library.

Any solutions for that?

Originally created by @ghost on GitHub (May 3, 2024). Original GitHub issue: https://github.com/abh/geodns/issues/143 Hello there, I found out that querying txt with long results will not work on this library. Any solutions for that?
kerem commented 2026-03-13 14:50:00 +03:00
Author
Owner
Copy link

@ghost commented on GitHub (May 3, 2024):

https://github.com/miekg/dns/issues/1566

<!-- gh-comment-id:2093686923 --> @ghost commented on GitHub (May 3, 2024): https://github.com/miekg/dns/issues/1566
kerem commented 2026-03-13 14:50:05 +03:00
Author
Owner
Copy link

@abh commented on GitHub (May 3, 2024):

That's a protocol limitation, no? You need to break the record into multiple smaller pieces.

<!-- gh-comment-id:2093896990 --> @abh commented on GitHub (May 3, 2024): That's a protocol limitation, no? You need to break the record into multiple smaller pieces.
kerem commented 2026-03-13 14:50:10 +03:00
Author
Owner
Copy link

@ghost commented on GitHub (May 4, 2024):

@abh Even when breaking into smaller sections, it creates double records, we do store encrypted text in txt records, when the recursive resolvers cache responses the order is not as we defined, I managed to fix all the issues, if you had time you can take a look into my repo and I can open a pull request if you want, https://github.com/matiniamirhossein/geodns

<!-- gh-comment-id:2093897971 --> @ghost commented on GitHub (May 4, 2024): @abh Even when breaking into smaller sections, it creates double records, we do store encrypted text in txt records, when the recursive resolvers cache responses the order is not as we defined, I managed to fix all the issues, if you had time you can take a look into my repo and I can open a pull request if you want, https://github.com/matiniamirhossein/geodns
kerem commented 2026-03-13 14:50:15 +03:00
Author
Owner
Copy link

@ghost commented on GitHub (May 12, 2024):

But the order will be correct in that case, that was the reason.

<!-- gh-comment-id:2106296278 --> @ghost commented on GitHub (May 12, 2024): But the order will be correct in that case, that was the reason.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
copilot/fix-102
avro
dependabot/go_modules/golang.org/x/net-0.7.0
master
godep
docs
geoip6
influxdb
targeting
edns-subnet
v3.4.1
v3.4.0
v3.3.3
v3.3.2
v3.3.1
v3.3.0
v3.2.3
v3.2.2
v3.2.1
v3.2.0
v3.1.0
v3.1.0-rc1
v3.0.2
v3.0.1
2.7.0
2.6.0
2.5.0
2.4.0
2.4.4
2.4.1
2.2.8
2.2.7
2.2.6
2.2.5
2.2.4
2.2.3
2.2.2
2.2.1
Labels
Clear labels   
bug

   
bug

   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

  
question
No labels
bug
bug
enhancement
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/geodns#385
No description provided.