-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Apr 03, 2003 at 09:34:02AM -0600, Nathan E Norman wrote:
[rfc 1035, 3.3.9]
MX records cause type A additional section processing for the host
specified by EXCHANGE.
Thus, one can conclude that the authors of the DNS protocol intended
On Wed, Apr 02, 2003 at 09:22:31PM -0800, Paul Johnson wrote:
(Please reply to the list as others may run into this problem, too)
On Wed, Apr 02, 2003 at 10:32:07PM -0500, Stephen Touset wrote:
Is that a limitation of ddclient? I've tried inputting the values
manually on their webpage,
In using ddclient, I've been trying to edit the configuration to allow
me to have a backup mx. After reading the help and man pages, I added
the following lines to my /etc/ddclient.conf file:
backupmx=yes
mx=smtp.domain.tld
I'm currently using the dyndns2 protocol to make the changes. However,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 02, 2003 at 09:58:34AM -0500, Stephen Touset wrote:
I'm currently using the dyndns2 protocol to make the changes. However,
even after adding this into the configuration file, a check on dyndns
(as well as using dig) confirms that no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 02, 2003 at 09:30:43PM -0500, Stephen Touset wrote:
What about using the IP address? Shouldn't that have worked? The DNS
alias though is neither a CNAME or an A record--it's an MX record in
that separate domain's records.
Nope. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Please reply to the list as others may run into this problem, too)
On Wed, Apr 02, 2003 at 10:32:07PM -0500, Stephen Touset wrote:
Is that a limitation of ddclient? I've tried inputting the values
manually on their webpage, and it works
6 matches
Mail list logo
