Hello. I've tested the dig command, and it is responding to the
_domainkey.sapucai.net. Thank you very much for your help.
On 8/22/06, Thomas Lamy <Thomas.Lamy@...> wrote:
> Jeffrey D. Wheelhouse wrote on Tuesday, August 22, 2006 5:43 PM:
> > Patrick Coleman wrote:
> > > Cool - mydnscheck should be easier to fix. Do you also see
> > issues with
> > > mydns itself when you use underscores? ie. even though mydnscheck
> > > complains, does mydns still serve up the domains?
> > >
> > > I will see if a patch to fix this is possible.
> > If you must, please make any such change a command line option (like
> > --ignore-invalid-hostnames, for example) that defaults to off. And,
> > while making such a change, you may as well skip the check
> > entirely, as
> > underscores aren't anywhere afforded any special status.
> > According to RFC 2181*, any eight-bit character is allowed, but only
> > when you're using the DNS for purposes other than resolving Internet
> > host names.
> > In general, neither mydnscheck nor mydns itself have the information
> > needed to determine whether a given record refers to a
> > hostname or not,
> > however it's safe to assume that the vast majority of them do. If
> > a record does refer to a hostname, then an underscore or any other
> > invalid character is an error and should be flagged as such.
> > Since very
> > nearly all records refer to hostnames, this check should exist and be
> > enabled by default.
> > Another approach would be to make more specific (and still
> > disabled by
> > default) exceptions for the obvious cases (--allow-_domainkeys and/or
> > possibly --allow-srv-underscores) where it's apparent the names in
> > question do not refer to Internet host names.
> > It's also worth noting that the underscore is used in MySQL LIKE
> > conditions as a one-character wildcard. I don't know if MyDNS performs
> > any such queries, but if it does, all sorts of problems could arise if
> > it's not properly escaped.
> > Thanks,
> > Jeff
> > *RFC 2181 is not an Internet Standard, it is a proposed standard. It
> > differs in this regard from RFC 1035 (Internet Standard
> > STD0013), which
> > expressly prohibits all characters other than the
> > alphanumerics and the
> > dash.
> I'd propose another approach: do not check for non-RFC1035-conformant
> chars in TXT rr's. This would apply to common practice, where TXT fields
> are commonly used for any types of antispam measures (domainkeys or
> Also, in SRV rr's underscores are only valid in the name, but not in the
> To make it "right" (from my pov), we need --allow-srv-underscores and
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> mydns-users mailing list