Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Cannot Find MX  (Read 2715 times)

matthewkoster

  • Newbie
  • *
  • Posts: 4
Cannot Find MX
« on: December 16, 2014, 10:01:49 AM »

Hello, I am trying to get to Administrator level, I have a Ubuntu 12.04 server set up with IPv6 and I have all the DNS done but when i try and send mail I get the following error: Unable to find MX for domain

I have to following set up in DNS
mydomain.com   SOA   86400   -   ns1.he.net. hostmaster.he.net. 2014121633 10800 1800 604800 86400
mydomain.com   NS   300   -   ns1.he.net      
mydomain.com   NS   300   -   ns2.he.net   
mydomain.com   NS   300   -   ns3.he.net      
mydomain.com   NS   300   -   ns5.he.net   
mydomain.com   NS   300   -   ns4.he.net   
mydomain.com   AAAA   300   -   <my IPv6 address>
mail.mydomain.com   AAAA   300   -   <my IPv6 address>
mydomain.com   MX   300   10   mail.mydomain.com   

However when I do a dig mydomain.com mx I get the following response:

# dig mydomain.com mx

; <<>> DiG 9.9.4-RedHat-9.9.4-14.el7_0.1 <<>> mydomain.com mx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45768
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;mydomain.com.      IN   MX

;; AUTHORITY SECTION:
mydomain.com.   770   IN   SOA   ns1.he.net. hostmaster.he.net. 2014121626 10800 1800 604800 86400

;; Query time: 0 msec
;; SERVER: 10.168.118.21#53(10.168.118.21)
;; WHEN: Tue Dec 16 12:56:40 EST 2014
;; MSG SIZE  rcvd: 106


NOTE:  I did have it set up wrong originally, if I dig mx.mydomain.com MX I get the following:\

# dig mx.mydomain.com mx

; <<>> DiG 9.9.4-RedHat-9.9.4-14.el7_0.1 <<>> mx.mydomain.com mx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49115
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 2

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;mx.mydomain.com.   IN   MX

;; ANSWER SECTION:
mx.mydomain.com. 20000   IN   MX   10 mydomain.com.

;; ADDITIONAL SECTION:
mydomain.com.   20000   IN   AAAA  <my ipv6 address>

;; Query time: 23 msec
;; SERVER: 10.168.118.21#53(10.168.118.21)
;; WHEN: Tue Dec 16 12:57:37 EST 2014
;; MSG SIZE  rcvd: 96


How long till the DNS corrects itself?  I have removed mx.mydomain.com and have placed mail.mydomain.com... I am using dns.HE.net's service
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2726
Re: Cannot Find MX
« Reply #1 on: December 16, 2014, 10:30:15 AM »

Might be easiest to email ipv6@he.net and ask them to flush the cache
Logged

matthewkoster

  • Newbie
  • *
  • Posts: 4
Re: Cannot Find MX
« Reply #2 on: December 16, 2014, 11:02:17 AM »

It seems to have resolved itself.  And some how I made it to Sage... Still need to do all the daily tests tho... thats gonna take a while.
Logged

kcochran

  • Sr. Network Engineer, Hurricane Electric
  • Administrator
  • Sr. Member
  • *****
  • Posts: 418
Re: Cannot Find MX
« Reply #3 on: December 16, 2014, 11:07:50 AM »

Test cache has an enforced hour max TTL on all lookups.  Doesn't matter the remote TTL.
Logged