Message Board

Donating MX Entries

Older Posts ]   [ Newer Posts ]
 Tried MX record, tried subdelegation...
Author: T.Martin   (9 Nov 04 9:16am)
...and nothing seems to be working.

When I initially submitted the MX donations, I tried it as an MX record inside the primary domain - for example:

schlep 3600 MX 10 mx6.mxmailer.com.

However, I got back an error from verification that said:

In order for this donation to be effective, you must point all the name servers controlling schlep.arisiasoft.com to our mail servers at mx6.mxmailer.com. The specific problem we have identified with your DNS modifications for this donation is that it appears that you have changed some, but not all of your name servers. While we found that you had correctly modified the settings for at least one of your name server(s), you must modify all the name servers that are responsible for this domain in order for this donation to be completed. It is possible that the modifications to the additional name server have yet to be picked up in which case we will check again over the next few days.

Note that the primary and all secondary servers for this domain were updated at this point.

So, I decided to try a subdelegation and see if that made a difference. I set up the subdelegation for schlep off the primary domain name, and added the appropriate records- to wit:

;
; Database file schlep.arisiasoft.com.dns for schlep.arisiasoft.com zone.
; Zone version: 2004103101
;

@ IN SOA ns0.arisiasoft.com. postmaster.arisiasoft.com. (
2004103101 ; serial number
7200 ; refresh
1800 ; retry
1209600 ; expire
86400 ) ; minimum TTL

;
; Zone NS records
;

@ 3600 NS ns0.arisiasoft.com.
@ 3600 NS ns1.arisiasoft.com.
@ 3600 NS ns2.arisiasoft.com.

;
; Zone records
;

@ 3600 MX 10 mx6.mxmailer.com.

Note that I also added the subdelegation and glue records at the parent domain.

I resubmitted the MX for verification, and a week later I got back a generic failure message (didn't say why it failed, only that it was being marked inactive).

I've verified the subdelegation (including the MX entry) at www.dnsreport.com and it seems to check out just fine.

Can someone give me an idea of what I've got wrong here?

Tracy
 
 Re: Tried MX record, tried subdelegation...
Author: L.Holloway   (9 Nov 04 6:29pm)
I ran some dig commands against the nameservers and got some varying results. If dig fails on one of the NS queries the MX will fail our test. We test each MX several times before deactivating it.

Here is the output:

NS0 FAILED:
[q@i8200:~/dev_hp/scripts]$ dig @ns0.arisiasoft.com schlep.arisiasoft.com MX

; <<>> DiG 9.2.1 <<>> @ns0.arisiasoft.com schlep.arisiasoft.com MX
;; global options: printcmd
;; connection timed out; no servers could be reached

NS1 FAILED:
[q@i8200:~/dev_hp/scripts]$ dig @ns1.arisiasoft.com schlep.arisiasoft.com MX

; <<>> DiG 9.2.1 <<>> @ns1.arisiasoft.com schlep.arisiasoft.com MX
;; global options: printcmd
;; connection timed out; no servers could be reached


NS1 OK:
[q@i8200:~/dev_hp/scripts]$ dig @ns1.arisiasoft.com schlep.arisiasoft.com MX

; <<>> DiG 9.2.1 <<>> @ns1.arisiasoft.com schlep.arisiasoft.com MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11804
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;schlep.arisiasoft.com. IN MX

;; ANSWER SECTION:
schlep.arisiasoft.com. 3600 IN MX 10 mx6.mxmailer.com.

;; Query time: 1430 msec
;; SERVER: 66.219.172.36#53(ns1.arisiasoft.com)
;; WHEN: Tue Nov 9 13:04:01 2004
;; MSG SIZE rcvd: 68


NS2 OK:
[q@i8200:~/dev_hp/scripts]$ dig @ns2.arisiasoft.com schlep.arisiasoft.com MX

; <<>> DiG 9.2.1 <<>> @ns2.arisiasoft.com schlep.arisiasoft.com MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20191
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;schlep.arisiasoft.com. IN MX

;; ANSWER SECTION:
schlep.arisiasoft.com. 3600 IN MX 10 mx6.mxmailer.com.

;; Query time: 1652 msec
;; SERVER: 66.219.172.39#53(ns2.arisiasoft.com)
;; WHEN: Tue Nov 9 13:04:15 2004
;; MSG SIZE rcvd: 68


NS0 OK: (later attempt)
[q@i8200:~/dev_hp/scripts]$ dig @ns0.arisiasoft.com schlep.arisiasoft.com MX

; <<>> DiG 9.2.1 <<>> @ns0.arisiasoft.com schlep.arisiasoft.com MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43963
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;schlep.arisiasoft.com. IN MX

;; ANSWER SECTION:
schlep.arisiasoft.com. 3600 IN MX 10 mx6.mxmailer.com.

;; Query time: 4374 msec
;; SERVER: 66.219.172.37#53(ns0.arisiasoft.com)
;; WHEN: Tue Nov 9 13:04:24 2004
;; MSG SIZE rcvd: 68


NS1 FAILS:
[q@i8200:~/dev_hp/scripts]$ dig @ns1.arisiasoft.com schlep.arisiasoft.com MX

; <<>> DiG 9.2.1 <<>> @ns1.arisiasoft.com schlep.arisiasoft.com MX
;; global options: printcmd
;; connection timed out; no servers could be reached


Your records are conifgured perfectly. The NS servers just seem a bit slow to respond sometimes. (Dig's default timeout is at least 8 seconds.)
 
 Re: Tried MX record, tried subdelegation...
Author: L.Holloway   (9 Nov 04 6:30pm)
I just ran schelp.arisiasoft.com through our MX tester program on a dev site. It passed on the 4th attempt, so what you can do is log in and reset the MX donation -- hopefully one of the attempts will go through...
 
 Re: Tried MX record, tried subdelegation...
Author: T.Martin   (10 Nov 04 10:29am)
Hmm... I've had intermittant reports of incoming connectivity problems, but have never been able to track down the reasons for them. Everything locally tests out fine, and my provider can't seem to see any problems either.

I'll reset the entries and see what happens. If it doesn't work out, well, won't be because I didn't try...:)
 
 Re: Tried MX record, tried subdelegation...
Author: L.Holloway   (10 Nov 04 5:06pm)
We certainly appreciate the attempt!



do not follow this link

Privacy Policy | Terms of Use | About Project Honey Pot | FAQ | Cloudflare Site Protection | Contact Us

Copyright © 2004–17, Unspam Technologies, Inc. All rights reserved.

contact | wiki | email