Force external dns for a domain.

M

marandia

Verified User
Joined
Jun 10, 2005
Messages
12
Location
Valencia, Spain
In 5 years using DA, this is the first time we've got this situation:

We have a customer that only wants to host with us the website (dns and e-mail are hosted outside our network)

We have checked out the option to use local mail server, but this force us to keep in our local dns records of the customer the MX data of the domain updated.

There is any way to skip that and the system checks directly the parent nameservers of the domain.

(Configuration of the domain are with correct dns information of the primary host, but system continues checking for mx records in local database)

Best Regards,
 
Do you have your own DNS server listed in your resolv.conf file? You really shouldn't; you should be using an external resolving DNS server (generally supplied by your upstream).

If you don't have any resolving DNS servers available to you, then you can try Google Public DNS; it works well for us.

Once you're using another resolving DNS server besides your own, then it doesn't matter what's in the DNS records for the domain on your server, as no one, not even your own server, will see them.

Jeff
 
Thank you Jeff for your fast reply ;-)

This is was the trouble. I had external dns, but also internal (127.0.0.1). I have erased local and now works OK.

By other way, I get this result when I do a basic test to the domain:

router = lookuphost, transport = remote_smtp
host XX.XX.XX.XX [unknown] MX=10 ** unusable **
host XX.XX.XX.XX [unknown] MX=20 ** unusable **
host mx2.domain.net [XX.XX.XX.XX] MX=30

I understand that the 2 first ones are unusable because mx records point to IP adresses and not to hostnames.

Thank you!
 
MX records that point to IP#s rather than to hostnames will eventually cause problems.

Fix them.

Jeff
 
Thank you, I know it, but the domain it's outside our control...

Thanks for your reply, and your great collaboration on this forum.

Regards,
 
marandia said:
Thank you, I know it, but the domain it's outside our control...
Click to expand...
Which is exactly why you should use a hostname rather than an IP#. If you use an IP#, and it ever changes, email will no longer work.

As is you'll find a lot of legitimate senders won't send mail to a domain with an mx record defined as an IP#.

Jeff
 
You must log in or register to reply here.
Back
Top