DNS TXT Record Splitter
Lambi TXT value ko DNS ke 255-byte strings mein kaatiye, zone file ke liye taiyaar.
DNS TXT Record Splitter poori tarah aapke browser mein chalta hai. Key aur verification token aapke device par hi kate jaate hain.
DKIM record banayiye
DNS TXT Record Splitter ke baare mein
TXT record ek lambi string nahi hai. RFC 1035 use character-strings ki shrinkhala ki tarah rakhta hai, har ek zyada se zyada 255 byte, aur resolver unhe bina kisi cheez ke jod deta hai. Isiliye 2048-bit DKIM key ko zone file mein kai quoted tukdon mein dena padta hai, aur isiliye galat jagah kaatna — ya tukdon ko space se jodna — mail signing ko aise todta hai jise dhoondhna mushkil hota hai. Ye tool byte boundary par kaatta hai, kabhi character ke beech nahi, aur nateeja BIND, parenthesised entry ya JSON array mein deta hai.
Features
- 255-byte boundary par kaatta hai, character nahi byte ginta hai
- Multi-byte character ya surrogate pair kabhi nahi todta
- BIND single line, parenthesised, sirf quoted strings ya JSON array format
- Har tukde ki byte ginti, taaki bhare hue string dikhein
- Extra whitespace, pehle se lage quotes aur 512 byte se bade record ki chetavni
- Zone file ya dig output ke quoted strings wapas jodta hai
- 2048-bit DKIM, lambe SPF aur verification token ke sample
DNS TXT Record Splitter kaise use karein
- Poori TXT value paste kijiye — quotes apne aap lag jaate hain
- Record name aur TTL daaliye agar poori zone line chahiye
- Apne DNS provider ke hisaab se output format chuniye
- Record copy kijiye, ya join tab se bati hui value wapas jodiye
Example
Input
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A… (392 bytes)
Output
default._domainkey 3600 IN TXT "v=DKIM1; k=rsa; p=MIIBIja…" "…QIDAQAB"
Do quoted strings, jinhe resolver bina kisi cheez ke jod deta hai.
Common errors aur troubleshooting
- DNS provider record ko bahut lamba keh kar mana kar deta hai. — Wo 255-byte seema ek hi string par laga raha hai. Bati hui version paste kijiye, har tukda alag quotes mein.
- Baantne ke baad DKIM verification fail ho raha hai. — Lagbhag hamesha tukdon ke beech space hota hai. Resolver strings ko bina kisi cheez ke jodte hain, isliye koi bhi space key ka hissa ban jaata hai.
- Record value mein pehle se quotes hain. — Kachchi value paste kijiye. Quotes format karte samay lagte hain, aur pehle se quoted value do baar quote ho jaati hai.
- Tukde 255 character se chhote hain. — Seema 255 byte ki hai, character ki nahi. Koi bhi non-ASCII character do se chaar byte leta hai, isliye tukda bhara hote hue bhi kam character rakh sakta hai.
Aksar pooche jaane wale sawaal
- TXT record 255 character tak seemit kyun hai?
- TXT record ke har string ke aage ek byte ki length hoti hai, jo string ko 255 byte tak baandhti hai. Poora record kai string rakh sakta hai, isliye asli seema DNS message ka size hai.
- Resolver bati hui TXT strings kaise jodta hai?
- Wo unhe kram se bina kisi separator ke jod deta hai. Isi vyavhaar par DKIM, SPF aur verification token tike hain, isliye kaatne ki jagah maayne nahi rakhti.
- DKIM key kahan kaatni chahiye?
- Kahin bhi, bas har tukda 255 byte se zyada na ho. Verifier ke liye jodne ke baad key ek hi Base64 string hoti hai, isliye Base64 ke beech kaatna theek hai.
- Poora TXT record kitna bada ho sakta hai?
- Vyavhaar mein kuchh kilobyte, par lagbhag 512 byte se badi answer ko EDNS ya TCP retry chahiye. Kuchh resolver isse theek se nahi sambhaalte, isliye chhota rakhna behtar hai.
- Kya SPF record ko bhi isi tarah baantna padta hai?
- Tabhi jab ek string 255 byte paar kare, jo kai include ke saath hota hai. Dhyaan rahe ki SPF ki apni das DNS lookup wali seema alag hai, jisme baantna madad nahi karta.
Related tools
Saare ArrayKit tools