DNS problem: www routed to base domain. how to fix?

[countchocula]

Hello,

My

http://www.example.com

dns resolution is having an unending round-robin problem. Any help is greatly appreciated!

I host my website (let's say example.com) at 000webhost.com, and I host my dns at Xname.org. I point subdomains to 000webhost.com's ns servers:

; <<>> DiG 9.3.4-P1.2 <<>> axfr example.com @ns0.xname.org.

example.com.		86400	IN	SOA	ns0.xname.org. xname.example.com. 2011092701 10800 3600 604800 10800
example.com.		86400	IN	TXT	"v=spf1 include:blahblahblah.com ~all"
example.com.		86400	IN	NS	ns0.xname.org.
example.com.		86400	IN	NS	ns1.xname.org.
example.com.		86400	IN	NS	ns1.secondarydomain.com.
example.com.		86400	IN	NS	ns2.xname.org.
example.com.		86400	IN	MX	1 ASPMX.L.GOOGLE.com.
example.com.		86400	IN	MX	5 ALT1.ASPMX.L.GOOGLE.com.
example.com.		86400	IN	MX	5 ALT2.ASPMX.L.GOOGLE.com.
example.com.		86400	IN	MX	10 ASPMX2.GOOGLEMAIL.com.
example.com.		86400	IN	MX	10 ASPMX3.GOOGLEMAIL.com.
google._domainkey.example.com. 86400 IN	TXT	"v=DKIM1\; k=rsa\; t=y\; p=blahblahblah"

calendar.example.com.	86400	IN	CNAME	ghs.GOOGLE.com.
docs.example.com.	86400	IN	CNAME	ghs.GOOGLE.com.
mail.example.com.	86400	IN	CNAME	ghs.GOOGLE.com.
sites.example.com.	86400	IN	CNAME	ghs.GOOGLE.com.

[URL unfurl="true"]www.example.com.[/URL]	86400	IN	NS	ns01.000webhost.com.
subdom1.example.com.		86400	IN	NS	ns01.000webhost.com.
subdom2.example.com.	86400	IN	NS	ns01.000webhost.com.

example.com.		86400	IN	SOA	ns0.xname.org. xname.example.com. 2011092701 10800 3600 604800 10800

As you can see, I also have other CNAME and MX records that point to other places online.

This all works for the most part. However, 000webhost.com nameservers have a CNAME for

http://www.example.com,

and they rewrite

http://www.example.com

to just example.com when the dns resolver request for

http://www.example.com

comes their way:

$ dig @ns01.000webhost.com [URL unfurl="true"]www.example.com[/URL]

; <<>> DiG 9.7.1 <<>> @ns01.000webhost.com [URL unfurl="true"]www.example.com[/URL]
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35142
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;[URL unfurl="true"]www.example.com.[/URL]               IN      A

;; ANSWER SECTION:
[URL unfurl="true"]www.example.com.[/URL]        172800  IN      CNAME   example.com.
example.com.            172800  IN      A       31.170.160.195

;; AUTHORITY SECTION:
example.com.            172800  IN      NS      ns01.000webhost.com.
example.com.            172800  IN      NS      ns02.000webhost.com.

;; ADDITIONAL SECTION:
ns01.000webhost.com.    172800  IN      A       208.43.152.32
ns02.000webhost.com.    172800  IN      A       64.120.10.10

What ends up happening is that, when you type

http://www.example.com

into your web broswer, it goes to 000webhost, which then rewrites it to example.com, so it goes back to xname.org, and back and forth, over and over again. What can I do in my DNS server (i.e. xname.org) to make sure that DNS resolver requests for http traffic for example.com end up going to ns01.000webhost.com also? Perhaps I do a CNAME for example.com that points to ns01.000webhost.com? I just need to do it in a way that won't screw up my other MX and CNAME records that point to places that *aren't* 000webhost.com.

Any help is greatly appreciated! thanks!

thanks!