lication date of that RFC (July 1997).
>
> - Kevin
>
> On 8/20/2013 3:14 PM, Nidal Shater wrote:
> > we know that BIND eleminate duplicate records, which version of BIND
> > that doesn't do that ?
> > NIDAL
--
Mark Andrews, ISC
1 Seymour St
Since such behavior would flagrantly violate RFC 2181, Section 5, look
for a version prior to the publication date of that RFC (July 1997).
- Kevin
On 8/20/2013 3:14 PM, Nidal Shater wrote:
we know that BIND eleminate duplicate records, which version of BIND
that doesn
we know that BIND eleminate duplicate records, which version of BIND that
doesn't do that ?
NIDAL
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-
On Dec 21, 2012, at 8:45 AM, Marek Kozlowski wrote:
> As I can see BIND allows duplicate A:
>
> pikusIN A 192.168.1.1
> pikusIN A 192.168.1.2
Those aren't duplicates. They are a record set of two records. If they had the
same data, we would call them duplicates.
A record set is a set of
:-)
As I can see BIND allows duplicate A:
pikusIN A 192.168.1.1
pikusIN A 192.168.1.2
and PTR:
192.168.1.1.IN PTR pikus.somedomain.com.
192.168.1.1.IN PTR filemon.somedomain.com.
and disallows duplicate CNAMEs in the same way. For A and PTR both
records are returned. My question
5 matches
Mail list logo