On Mon, 27 Apr 2009, Karsten Br?ckelmann wrote:
y.real-at999.z @ a.at.real-at2.bc ->
y.real-at999.z.real-at1000.a.at.real-at2.bc
Still ambiguous. So the generated s/at/real-at$n/ is the last occurrence
of a numbered "real-at" plus 1.
What if we need it twice, and there are 3 such thingies in total? How do
we know we only need to "decode" 1 -- or do we need to decode2? Or maybe
even all three, if they start at 1...
Sorry, Adam. ;)
How about "_at_" - I think a leading and trailing underscore will be very
rare in real world domain name parts, especially as you can't register
a domain name having an underscore, and may apps will discard hostnames
with underscores as invalid.
Will the DNS server choke on that? Remember, it only has to be valid
within the scope of a DNS query.
y.real-at999.z @ a.at.real-at2.bc ->
y.real-at999.z._at_.a.at.real-at2.bc
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
A sword is never a killer, it is but a tool in the killer's hands.
-- Lucius Annaeus Seneca (Martial) 4BC-65AD
-----------------------------------------------------------------------
96 days since Obama's inauguration and still no unicorn!
