• 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.

DNS Not Working in Plesk

E

erichhaubrich

Guest
I have tried several configurations for my DNS settings and have yet to have any success. I have two sites hosted on my server which work fine - they are not using my nameservers, but when I try to point a domain to ns1.maindomain.net I get no results. All other services on the box run fine, but DNS just won't work. (Please note - I am using maindomain.net as an example)

I tested the nameservers by going to http://www.dns.lu/en/EN-LUTestNoms.php and filling in all the proper info and got the following results:

Error: Nameserver test failed
Info: Nameserver test for domain otherdomain.com
Note: Nameserver ns1.maindomain.net at XX.XXX.23.230 (provided)
Note: Nameserver ns2.maindomain.net at XX.XXX.23.229 (provided)
Error: No answer from ns2.maindomain.net at address XX.XXX.23.229
Error: No answer from ns1.maindomain.net at address XX.XXX.23.230
Error: No working authoritative nameserver found
Error: At least 2 nameservers required


Currently my server DNS settings are:

Host Record type Value
<domain>. NS ns1.maindomain.net.
<domain>. NS ns2.maindomain.net.
<domain>. A XX.XXX.23.230
<domain>. MX (10) mail.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
ns1.<domain>. A XX.XXX.23.230
ns2.<domain>. A XX.XXX.23.229
webmail.<domain>. A <ip>


I did a reverse DNS check and go these results:

XX.XXX.23.230 resolves to
"ns1.maindomain.net"
Top Level Domain: "maindomain.net"


I did a WHOIS and got these results:

domain: otherdomain.com
created: 30-Jun-2006
last-changed: 01-Apr-2008
registration-expiration: 30-Jun-2008

nserver: ns1.maindomain.net XX.XXX.23.230
nserver: ns2.maindomain.net XX.XXX.23.229



I am stumped here and would appreciate any assistance.

I thought for sure there would be an answer in these forums, but oddly a search for "DNS" turned up absolutely nothing.
 
Try This

1. update your domain name, as it expires next month

2. [root@myserver ~]# dig 64bithost.com NS

; <<>> DiG 9.3.3rc2 <<>> 64bithost.com NS
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30645
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;64bithost.com. IN NS

;; ANSWER SECTION:
64bithost.com. 19 IN NS ns2.64bithost.com.
64bithost.com. 19 IN NS ns1.64bithost.com.

;; ADDITIONAL SECTION:
ns1.64bithost.com. 210 IN A 209.251.144.222
ns2.64bithost.com. 210 IN A 209.251.144.223

;; Query time: 2 msec
;; SERVER: 209.251.130.31#53(209.251.130.31)
;; WHEN: Mon Apr 14 02:10:27 2008
;; MSG SIZE rcvd: 99


3. your name servers should correspond directly to the i.p in the "A" record.
4. your NS records and I.P. records need to be registered with your registrar.

-Chris
 
Thanks for the effort, but this did not answer any of my questions and was actually erroneous because I did not offer my real domain name.
 
Make sure that the Windows DNS server is disabled and only plesk DNS is running. Just faced this issue on a clients server and was able to fix it by disabling DNS under Services.
 
Error: No answer from ns2.maindomain.net at address XX.XXX.23.229
Error: No answer from ns1.maindomain.net at address XX.XXX.23.230

is your nameserver up and running ?
is there a firewall blocking nameservice ?
 
Back
Top