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

Need to delgate subdomain ?

Started by eludom, October 10, 2010, 02:02:39 PM

Previous topic - Next topic

eludom

I have a domain (hosted with he.net) that I've been using for a long time with MX
records pointing at Google Hosting.

I've set up an AAAA record for a host (ipv6.port111.com) and all is fine.

When I add an MX for ipv6.port111.com, it fails to show up in dig.   Do I need
to delegate a domain ?   Can I do this in the context of the he.net zoneedit
tool ?

Thanks,
---George Jones

cholzhauer

How long did you let it propagate?



[carl@mars ~]$ dig mx ipv6.port111.com

; <<>> DiG 9.6.2-P2 <<>> mx ipv6.port111.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32953
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;ipv6.port111.com.              IN      MX

;; ANSWER SECTION:
ipv6.port111.com.       3575    IN      MX      10 ipv6.port111.com.

;; ADDITIONAL SECTION:
ipv6.port111.com.       3593    IN      AAAA    2001:470:7:78d::2

;; Query time: 123 msec
;; SERVER: 2001:470:c27d:e000:41bd:d9bf:9b66:9b95#53(2001:470:c27d:e000:41bd:d9bf:9b66:9b95)
;; WHEN: Sun Oct 10 17:52:28 2010
;; MSG SIZE  rcvd: 78


HE seems to know about it too


[carl@mars ~]$ dig mx ipv6.port111.com @2001:470:200::2

; <<>> DiG 9.6.2-P2 <<>> mx ipv6.port111.com @2001:470:200::2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1389
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;ipv6.port111.com.              IN      MX

;; ANSWER SECTION:
ipv6.port111.com.       3600    IN      MX      10 ipv6.port111.com.

;; ADDITIONAL SECTION:
ipv6.port111.com.       3600    IN      AAAA    2001:470:7:78d::2

;; Query time: 97 msec
;; SERVER: 2001:470:200::2#53(2001:470:200::2)
;; WHEN: Sun Oct 10 17:53:09 2010
;; MSG SIZE  rcvd: 78


eludom

It was indeed impatience that was the problem :-).

Currently trying to figure out where to point AAAA/NS records (e.g. ns1.he.net's v6 equivilant) ... no wait....
dig is your friend:

dig ns1.ipv6.he.net any

; <<>> DiG 9.7.0-P1 <<>> ns1.ipv6.he.net any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30684
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ns1.ipv6.he.net.      IN   ANY

;; ANSWER SECTION:
ns1.ipv6.he.net.   400   IN   A   64.71.188.2
ns1.ipv6.he.net.   400   IN   AAAA   2001:470:0:57::2

Thanks,
---George