|
Hello, I seem to be having trouble with setting up MX records for my domain within Custom DNS. I am going to point a domain at DYNDNS's nameservers and, well, I want to be sure this is all working before I do the deed. I created a record within the Expert Interface. It shows something like this: I've pre-activated the service for testing. I've pointed my own workstation's NSLOOKUP at http://ns1.mydyndns.org and can query A and CNAMEs without a problem. But when I query the MX records for http://domain.com, I receive: So, I'm a bit lost as to the cause. I've written tech support, but they're really pushing this forum, soooo... :-) Here is the exact stuff I am doing with NSLOOKUP: |
This would have to point to your mail exchanger, in case you have one. "domain.com.s7a1.psmtp.com" does not look as if you are the owner of http://psmtp.com. So I presume you are hosting your mail exchanger somewhere else. As you do not discover your zone/domain name, nobody can really help, as this is a user forum. The domain is http://sugarcreekcctexas.com. Our mail servers are at Postini/Google. So, yes, the mail exchanger is somewhere else. :-)
Mar 10 at 01:47 PM
tcv
|
|
CNAMEs explicitly won't work for MX records. Now, do you have your domain registered and in the domain registration have you configured the Custom DNS DNS servers? If you can post your real domain then those of us with more experience can do some diagnostics for you. The domain is registered at GoDaddy and I plan to leave it there and set the NAMESERVERS to the http://mydyndns.org servers. The domain is "sugarcreekcctexas.com." When I said that "CNAMEs" don't work either, I am saying that when I use NSLOOKUP to query for a CNAME at http://ns1.mydyndns.org (e.g. http://mail.sugarcreekcctexas.com) I receive a big list of ROOT servers, not the IP address I expect.
Mar 10 at 01:46 PM
tcv
|
|
I think I just saw this ticket in the support queue (1191657). For future reference for other http://DynCommunity.com members, my best guess is that he had just created his Custom DNS zone and it hadn't been preactivated yet, so the zone file wasn't loaded. Looking at the times he purchased the service and stuff, that appears to have been what happened. Thus when he queried our servers, there was no response since there were no records loaded on our servers yet. Good news that it has since pre-activated and the zone is loaded on our servers, I am able to query its MX records. I won't post the domain unless the customer decides to do it themselves, but it looks all set from my end. Very strange. I am on Windows. Could that account for behavior differences? I've also tried a completely different workstation outside of the network I'm currently in, but that system, too, was running Windows.
Mar 10 at 03:19 PM
tcv
Hmmm... If I sent WINDOWS' NSLOOKUP to "nosearch," then I get proper results from DYNDNS' nameservers. I've also installed BIND's tools here and am also getting proper results. What is this search thing in Windows?
Mar 10 at 05:33 PM
tcv
Simply enter this: nslookup -type=mx http://sugarcreekcctexas.com.
Mar 10 at 05:39 PM
RotBlitz ♦
It could be that the old values are still within their TTL and so still in your caches. Try flushing the DNS cache (
Mar 10 at 05:46 PM
Cry Havok ♦
Rot: I can't simply use that command because that wouldn't query DYNDNS nameservers. Cry: Flushing the cache doesn't work. The only thing that seems to work is to "set nosearch" within the Windows version of NSLookup. I just need to understand what that is...
Mar 10 at 05:53 PM
tcv
|
|
At this point in time your name servers are still set to be the GoDaddy ones. Querying the DynDNS name servers directly shows your MX records: |
Originator hasn't returned to this question in a month, closing to stop the forum bot bumping it.