• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue DNS loop problem

djdavey

New Pleskian
Hi there,

I am suddenly having a problem with the main domain on my Plesk server.

DNS diagnostic tools are saying "DNS loop detected".

I have the nameservers with IP set up with my registrar, and the DNS record in Plesk for the domain, all seems in order.

I have also checked the file under /var/named/chroot/domain.com, no problems there either.

Where else could there be a problem? Any suggestions? I don't know where to go from here.

Thanks in advance for your help.

System info:

OS‪CentOS Linux 7.2.1511 (Core)‬
Plesk version12.5.30 Update #51, last updated at Oct 28, 2016 03:15 AM



Here is the dns file from /var/named/chroot/domain.com (IP-Address is correct, domain.com is correct)




; *** This file is automatically generated by Plesk ***

$TTL 86400


@ IN SOA ns1.domain.com. dave.domain.com. (

1478035701 ; Serial

10800 ; Refresh

3600 ; Retry

604800 ; Expire

10800 ) ; Minimum

IP-Address / 24 PTR domain.com.

ns2.domain.com. A IP-Address

ipv4.domain.com. A IP-Address

domain.com. A IP-Address

domain.com. MX (5) ALT1.ASPMX.L.GOOGLE.COM.

domain.com. MX (5) ALT2.ASPMX.L.GOOGLE.COM.

domain.com. MX (0) ASPMX.L.GOOGLE.COM.

www.domain.com. CNAME domain.com.

ftp.domain.com. CNAME domain.com.

domain.com. NS ns2.domain.com.

domain.com. MX (10) ASPMX2.GOOGLEMAIL.COM.

domain.com. MX (10) ASPMX3.GOOGLEMAIL.COM.

media.domain.com. CNAME s3-eu-west-1.amazonaws.com.

ns1.domain.com. A IP-Address

em.domain.com. CNAME cname.createsend.com.

domain.com. MX (10) ASPMX5.GOOGLEMAIL.COM.

domain.com. MX (10) ASPMX4.GOOGLEMAIL.COM.

domain.com. NS ns1.domain.com.
 
Okay it appears my /etc/resolv.conf file has been overwritten, showing as modified at the same time as the last reboot. I should add that I am running Plesk on AWS.

current contents of resolv.conf:

; generated by /usr/sbin/dhclient-script

search eu-west-1.compute.internal

nameserver 10.0.0.2

Could this be my problem? I'm no DNS expert... What should this file contain? Is there anything else I should look for? I ran "plesk repair web" and "plesk repair dns" but no errors, warnings or resolutions and the site remains unreachable - ERR_NAME_NOT_RESOLVED.

Thanks
 
Back
Top