bel, for example
one derived from a 128-bit random number.
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
y as a DNSOP
participant, as a third-party notification under RFC 3979 section
6.1.3, because I thought the working group should be aware that the
patent exists. I am not currently affiliated with Nominum and did not
submit the statement on their behalf nor at their request.
--
Andreas Gustafsson, g..
the configured root
servers while priming is in progress.
There is nothing wrong with existing resolvers that use the same
timeout and retransmission strategies for priming queries as for any
other query, and it seems wrong to me that a specific retransmission
timeout should be required for
DNS update
protocols other than RFC 2136 do exist, and now that you mentioned
Gandi, it reminds me that there's also the Amazon Route 53 API.
I'm sure there are many more.
> I will try to cover this kind of situation. Thanks for the discussion, it
> has
ld even be applied to tools that update zones through mechanized
editing of master files.
> Who here knows how Active Directory interacts with DNS aliases?
Not me...
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
FC2136, or a requirement on UPDATE clients in general.
I would even say that the requirement to follow CNAME and DNAME
redirections should apply equally when the updates are not performed
using the RFC2136 UPDATE protocol at all, but using some other
mechanism.
--
Andreas Gustafsson, g...@araneu
the same allowance for compatibility
> reasons.
Maybe such allowances had to be made at one point, but they are not
needed today. BIND 9 has been rejecting compression pointers to
"later occurrences" for 15 years now, so any implementation sending
them has surely been weeded out by now.
--
compress
> something they should not have compressed, should feel pain.
That would be good, yes, and it is allowed by 3597, but not required.
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
s is not limited to glue; the same issues arise with records
in the additional section and with CNAME chains.
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
r, and cheaper for the authoritative server to
respond to. Keeping state in the resolver is expensive, and the
memory would probably be better spend on other things such as a
larger cache.
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
e records in the response or not.
The situation of RCODE=0 and no records in the answer section is
sometimes referred to as NOERROR/NODATA (e.g., RFC6840 section 4.3) or
simply NODATA (RFC2308 section 2.2).
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP ma
lar ways, fixed.
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
Paul Hoffman wrote:
> Or, we could use an actual standards-track RFC: 4343.
That's a good find. Works for me.
> I take it no one remembers this one...
I must have mentally filed it under "Case Insensitivity" and
forgotten that it also discussed this issue.
--
t document is read by a standard
JSON decoder, they will result in identical string objects, and the
distinction will be lost.
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
the right thing:
the DNS library will translate the length-prefixed wire format strings
to dot-delimited ones *and* do \DDD escaping, and the JSON library
will add a set quotes around the string to make it a JSON string *and*
double any backslashes.
--
Andreas Gustafsson, g...@araneus.fi
__
le.com. RP john\.smith.example.com. .
a.example.com. TXT "one string"
b.example.com. TXT "two" "strings"
c.example.com. TXT "string with \"embedded\" quotes"
Regards,
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
n
pay ICANN the same application fee any other gTLD applicant would.
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
ot; is common usage for the
particular situation of "parent and child NS RRsets differ"
any more than "lame delegation" is, and as far as I know,
there is no established shorthand term that refers
specifically to this situation.
--
Andreas Gustafsson, g...@araneus.fi
_
abel is limited to between 1 and 63 octets. A full domain
name is limited to 255 octets (including the separators). The zero
length full name is defined as representing the root of the DNS tree,
and is typically written and displayed as ".". Those rest
as they rely on NXDOMAIN responses to indicate that
an address or name is not listed.
--
Andreas Gustafsson, g...@araneus.fi
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
haves as if
a wildcard had been added to every single zone in the DNS, not just
every TLD but also the root zone and every zone delegated from the
TLDs, including your own zones. This is indeed not just Site Finder
all over again - it's far worse, and breaks far more applications th
21 matches
Mail list logo
