From Newsgroup: comp.protocols.dns.bind
--00000000000017f89005a85bf375
Content-Type: text/plain; charset="UTF-8"
May I suggest the following?:
If you are an individual that is so pedantic that seeing a spelling error causes you to lose sleep or have other soul searing consternation, send an email (gently worded) to the poster only. Please also be encouraging to
that individual pointing out that these types of errors happen and will not cause loss of their immortal soul. As Ondrej points out, we are trying to
build community that's welcoming to newcomers to the wonderful world of DNS.
I remember when I first subscribed to this list being terrified of posting after reading several rather terse replies. I've since gotten a bit thicker skin. I've learned a lot from this list. However, it's not for the timid. Please be considerate in the wording of your replies.
With my lack of typing skills, my lack of spelling skills, and my lack of grammar skills, it's a small wonder that anything I post on this list is understood.
Couple that with most readers not having english as a first language and it quickly becomes a miracle!
My somewhat simpler interpretation of that error:
if during the named loading process a zone produces an error that says
CNAME and other data, my experience has been that the zone being loaded contains an A record and one or more CNAME records with the same owner
value (hostname). That's not allowed under the RFC documents for bind.
e.g.
remtest IN A 100.64.0.2
remtest IN CNAME temp.example.com.
-OR-
remtest IN CNAME temp.example.com.
remtest IN CNAME temp001.example.com.
Both examples are not allowed under the RFCs.
Bob
--00000000000017f89005a85bf375
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">May I suggest the following?:<div><br></div><div>If you ar=
e an individual that is so pedantic that seeing a spelling error causes you=
to lose sleep or have other soul searing consternation, send an email (gen= tly worded) to the poster only. Please also be encouraging to that individu=
al pointing out that these types of errors happen and will not cause loss o=
f their immortal=C2=A0soul. As Ondrej points out, we are trying to build co= mmunity that's welcoming to newcomers to the wonderful world of DNS.</d= iv><div><br></div><div>I remember when I first subscribed to this list bein=
g terrified of posting after reading several rather terse replies. I've=
since gotten a bit thicker skin. I've learned a lot from this list. Ho= wever, it's not for the timid. Please be considerate in the wording of = your replies.</div><div><br></div><div>With my lack of typing skills, my la=
ck of spelling skills, and my lack of grammar skills, it's a small wond=
er that anything=C2=A0I post on this list is understood.</div><div><br></di= v><div>Couple that with most readers not having english as a first language=
and it quickly becomes a miracle!</div><div><br></div><div>My somewhat sim= pler interpretation=C2=A0of that error:</div><div><br></div><div>if during = the named loading process a zone produces an error that says CNAME and othe=
r data, my experience has been that the zone being loaded contains an A rec= ord and one or more CNAME records with the same owner value (hostname). Tha= t's not allowed under the RFC documents for bind.</div><div><br></div><= div>e.g.</div><div><br></div><div>remtest IN A 100.64.0.2</div><div>remtest=
IN CNAME <a href=3D"
http://temp.example.com">temp.example.com</a>.</div><d= iv><br></div><div>-OR-</div><div><br></div><div>remtest IN CNAME <a href=3D= "
http://temp.example.com">temp.example.com</a>.</div><div>remtest IN CNAME =
<a href=3D"
http://temp001.example.com">temp001.example.com</a>.</div><div><= br></div><div>Both examples are not allowed under the RFCs.</div><div><br><= /div><div>Bob</div><div><br></div><div><br></div><div><br></div></div>
--00000000000017f89005a85bf375--
--- Synchronet 3.21d-Linux NewsLink 1.2