• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Unable to find AAAA for MX record.

Started by dzmodest, November 03, 2015, 07:58:40 AM

Previous topic - Next topic
Print
Go Down Pages1 2
User actions

dzmodest

November 03, 2015, 07:58:40 AM
Hi

i have fully setuped aaaa for mx record
and here is the dig results :
============================================================
root@p:~# dig AAAA propod.net

; <<>> DiG 9.8.1-P1 <<>> AAAA propod.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3483
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;propod.net.                    IN      AAAA

;; ANSWER SECTION:
propod.net.             299     IN      AAAA    2001:41d0:d:1590:0:d:132:1

;; Query time: 22 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov  3 15:56:16 2015
;; MSG SIZE  rcvd: 56
============================================================

also you can check using mxtoolbox service
http://mxtoolbox.com/SuperTool.aspx?action=mx%3apropod.net&run=toolpage


..
but in he.net test i'm getting this error :
3    Status:    Unable to find AAAA for MX record.

note : i have used email : admin@propod.net

Any advice ?

cholzhauer

#1
November 03, 2015, 08:00:20 AM
I can confirm your results.  How long ago did you make changes in DNS?  Sometimes it takes the test a while to see updates.

Code Select

$ drill mx propod.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 10500
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 2
;; QUESTION SECTION:
;; propod.net.  IN      MX

;; ANSWER SECTION:
propod.net.     300     IN      MX      0 propod.net.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:
propod.net.     300     IN      A       51.254.92.114
propod.net.     300     IN      AAAA    2001:41d0:d:1590:0:d:132:1

dzmodest

#2
November 03, 2015, 08:03:46 AM
Quote from: cholzhauer on November 03, 2015, 08:00:20 AM
I can confirm your results.  How long ago did you make changes in DNS?  Sometimes it takes the test a while to see updates.

Code Select

$ drill mx propod.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 10500
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 2
;; QUESTION SECTION:
;; propod.net.  IN      MX

;; ANSWER SECTION:
propod.net.     300     IN      MX      0 propod.net.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:
propod.net.     300     IN      A       51.254.92.114
propod.net.     300     IN      AAAA    2001:41d0:d:1590:0:d:132:1


Thanks for your fast reply :)
i made it less than one hour ago

cholzhauer

#3
November 03, 2015, 08:04:24 AM
I assume TTL is at least an hour, so you'll just have to sit and wait.

dzmodest

#4
November 03, 2015, 08:07:16 AM
Quote from: cholzhauer on November 03, 2015, 08:04:24 AM
I assume TTL is at least an hour, so you'll just have to sit and wait.

TTL is 300 (5mn)

how much i have to wait ?

dzmodest

#5
November 03, 2015, 08:33:41 AM
i have removed A record, it may help more ..
but still the same problem

could someone else check it ?

cholzhauer

#6
November 03, 2015, 08:34:34 AM
Removing the A record won't help.

You need to wait, sorry.

dzmodest

#7
November 03, 2015, 08:42:05 AM
Quote from: cholzhauer on November 03, 2015, 08:34:34 AM
Removing the A record won't help.

You need to wait, sorry.
Could you check the results of the following if they are fine or not
dig propod.net
dig MX propod.net
dig AAAA propod.net

this is my propod.net dns zone :
http://s11.postimg.org/6p89mz38j/propod_dns.png

cholzhauer

#8
November 03, 2015, 08:49:50 AM
Results I get match what you posted

dzmodest

#9
November 03, 2015, 08:51:59 AM
Quote from: cholzhauer on November 03, 2015, 08:49:50 AM
Results I get match what you posted
is it fine ?
and what about the dns zone looks good too ?

..
will he support help me if i contacted them ? they may flush cache/dns

cholzhauer

#10
November 03, 2015, 08:53:48 AM
I have no idea what it's supposed to look like.  Assuming the IP address you posted is correct, then yes.

You can open a ticket and have them look into it.  ipv6@he.net

dzmodest

#11
November 03, 2015, 08:57:41 AM
Quote from: cholzhauer on November 03, 2015, 08:53:48 AM
I have no idea what it's supposed to look like.  Assuming the IP address you posted is correct, then yes.

You can open a ticket and have them look into it.  ipv6@he.net

ok thanks, i have just created a ticket hope to get fast reply :)
..

still looking for a solution ..

broquea

#12
November 03, 2015, 09:28:31 AM
There is something very odd with the DNS of this domain. The authoritative name servers listed are:

Code Select
;; QUESTION SECTION:
;propod.net. IN NS

;; ANSWER SECTION:
propod.net. 75335 IN NS ns1.ihostadvance.com.
propod.net. 75335 IN NS ns2.ihostadvance.com.

However a dig +trace shows that HE name servers are answering:

Code Select
~$ dig AAAA propod.net +trace

; <<>> DiG 9.9.5-11ubuntu1-Ubuntu <<>> AAAA propod.net +trace
;; global options: +cmd
. 85836 IN NS c.root-servers.net.
. 85836 IN NS d.root-servers.net.
. 85836 IN NS k.root-servers.net.
. 85836 IN NS j.root-servers.net.
. 85836 IN NS b.root-servers.net.
. 85836 IN NS a.root-servers.net.
. 85836 IN NS i.root-servers.net.
. 85836 IN NS g.root-servers.net.
. 85836 IN NS l.root-servers.net.
. 85836 IN NS e.root-servers.net.
. 85836 IN NS h.root-servers.net.
. 85836 IN NS f.root-servers.net.
. 85836 IN NS m.root-servers.net.
;; Received 241 bytes from 127.0.1.1#53(127.0.1.1) in 21 ms

net. 172800 IN NS a.gtld-servers.net.
net. 172800 IN NS b.gtld-servers.net.
net. 172800 IN NS c.gtld-servers.net.
net. 172800 IN NS d.gtld-servers.net.
net. 172800 IN NS e.gtld-servers.net.
net. 172800 IN NS f.gtld-servers.net.
net. 172800 IN NS g.gtld-servers.net.
net. 172800 IN NS h.gtld-servers.net.
net. 172800 IN NS i.gtld-servers.net.
net. 172800 IN NS j.gtld-servers.net.
net. 172800 IN NS k.gtld-servers.net.
net. 172800 IN NS l.gtld-servers.net.
net. 172800 IN NS m.gtld-servers.net.
net. 86400 IN DS 35886 8 2

;; Received 731 bytes from 2001:500:1::803f:235#53(h.root-servers.net) in 86 ms

propod.net. 172800 IN NS ns1.he.net.
propod.net. 172800 IN NS ns2.he.net.

;; Received 623 bytes from 192.55.83.30#53(m.gtld-servers.net) in 194 ms

propod.net. 300 IN AAAA 2001:41d0:d:1590:0:d:132:1
;; Received 67 bytes from 216.218.131.2#53(ns2.he.net) in 1 ms

It looks like some sort of registrar conflict with where DNS is delegated. The caching name servers are trying to go to the cached authoritative name servers that expire after a week.

broquea

#13
November 03, 2015, 10:02:11 AM
I pinged the DNS team to reload the caching NS, seems fine now:

Code Select
~$ dig ns propod.net

; <<>> DiG 9.9.5-11ubuntu1-Ubuntu <<>> ns propod.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12218
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;propod.net. IN NS

;; ANSWER SECTION:
propod.net. 85897 IN NS ns4.he.net.
propod.net. 85897 IN NS ns2.he.net.
propod.net. 85897 IN NS ns3.he.net.
propod.net. 85897 IN NS ns5.he.net.
propod.net. 85897 IN NS ns1.he.net.


Making a change the day of, and not previously shortening the 86400 TTL was your issue.

dzmodest

#14
November 03, 2015, 11:37:21 AM
Quote from: broquea on November 03, 2015, 10:02:11 AM
I pinged the DNS team to reload the caching NS, seems fine now:

Code Select
~$ dig ns propod.net

; <<>> DiG 9.9.5-11ubuntu1-Ubuntu <<>> ns propod.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12218
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;propod.net. IN NS

;; ANSWER SECTION:
propod.net. 85897 IN NS ns4.he.net.
propod.net. 85897 IN NS ns2.he.net.
propod.net. 85897 IN NS ns3.he.net.
propod.net. 85897 IN NS ns5.he.net.
propod.net. 85897 IN NS ns1.he.net.


Making a change the day of, and not previously shortening the 86400 TTL was your issue.


Thank you, problem solved.
It works :)
Print
Go Up Pages1 2
User actions