Yahoo DNS conflict with Plesk DNS

Hi there, I am sure there is a simple answer to this one.

I have a client who's domain is registered with Yahoo. I have had to set up their MX records as well as 2 A records and 2 Cname records in order to get their site viewable on the web. Currently, my issue is the www.myclientsdomain.com points to the server root wich is forwarded to our company's website. That ain't no good! Further, FTP functionality is spotty at best. Some clients can connect, some cannot all using the same settings.

Usually, using a domain registrar such as godaddy or netsol, everything is peachy. Just point the primary and secondary nameservers and my Plesk setup handles the rest to point everything where it needs to be.

Unfortunately, Yahoo wants to control virtually everything with regards to DNS, hence the modified records on the Yahoo domain registrar level. If I remove a record, it will automatically point that to yahoo servers. ARRRGH!

Currently I have the MX records set up and running fine. Some of the A records are pointed correctly as http://myclientsdomain.com shows up for all parties.

I have the following set up for A records and Cnames in Yahoo:

A Record      myclientsdomain.com      111.111.111.111      
A Record      mail.myclientsdomain.com      111.111.111.111      
A Record      *.myclientsdomain.com      111.111.111.111      
CNAME Record      ftp.myclientsdomain.com             myclientsdomain.com      
CNAME Record      www.myclientsdomain.com      mydomain.com      

HEre is what is active in the Plesk admin panel DNS settings for this particular domain:

111.111.111.111 / 24      PTR      myclientsdomain.com.
myclientsdomain.com.      NS      ns1.mywebserver.com.
myclientsdomain.com.      NS      ns2.mywebserver.com.
myclientsdomain.com.      NS      ns3.mywebserver.com.
myclientsdomain.com.      NS      ns4.mywebserver.com.
myclientsdomain.com.      NS      ns5.mywebserver.com.
myclientsdomain.com.      A      216.139.234.120
mail.myclientsdomain.com.      A      111.111.111.111
ns.myclientsdomain.com.      A      111.111.111.111
webmail.myclientsdomain.com.      A      111.111.111.111
www.myclientsdomain.com.      CNAME      myclientsdomain.com.
iambgAsked:
Who is Participating?
 
iambgConnect With a Mentor Author Commented:
DNS through our windows server at my location was causing the issue. I had set everything correctly.
0
 
AdraenyseCommented:
First question before getting into the zones: On the domain name itself, are the name servers pointed to you or to Yahoo? I assume Yahoo, which means the DNS zone in Plesk is actually a bad thing. It's going to conflict by overriding any response from Yahoo with it's own records when doing any sort of local lookups.

If you can't point the domain back to your Plesk box, then you need to disable the DNS zone for the domain inside of Plesk. That way, your server will then query your Yahoo DNS zone for the proper responses.

Also:
A Record      *.myclientsdomain.com      111.111.111.111      

is not a valid DNS entry. You can't have wildcards as an A record. The only place you can use wildcards is in wildcard SSL certificates.
0
All Courses

From novice to tech pro — start learning today.