• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Custom Nameserver Creation Not Resolving

Eric Lowe

New Pleskian
Hello,

I've been through the Plesk admin guide as well as these and other forums for countless days trying to resolve this issue, unfortunately with no luck. After upgrading to Plesk 9.3 I cannot get the nameservers to work. The same nameservers worked fine in Plesk 8, so I'm not sure what I've done wrong.

I have in the DNS Zone Template -> DNS Settings
Code:
 <domain>. NS ns1.theshadowsembrace.com. 
 <domain>. NS ns2.theshadowsembrace.com. 
 <domain>. A <ip> 
 <domain>. MX (10) mail.<domain>. 
 <domain>. TXT v=spf1 +a +mx -all 
 <ip> / 24 PTR <domain>. 
 ftp.<domain>. CNAME <domain>. 
 mail.<domain>. A <ip> 
 webmail.<domain>. A <ip>

Under Domains -> theshadowsembrace.com
Code:
 66.148.68.119 / 24 PTR theshadowsembrace.com. 
 ftp.theshadowsembrace.com. CNAME theshadowsembrace.com. 
 mail.theshadowsembrace.com. A 66.148.68.119 
 ns1.theshadowsembrace.com. A 66.148.68.119 
 ns2.theshadowsembrace.com. A 66.148.68.119 
 theshadowsembrace.com. NS ns1.theshadowsembrace.com. 
 theshadowsembrace.com. NS ns2.theshadowsembrace.com. 
 theshadowsembrace.com. A 66.148.68.119 
 theshadowsembrace.com. MX (10) mail.theshadowsembrace.com. 
 theshadowsembrace.com. TXT v=spf1 +a +mx -all 
 webmail.theshadowsembrace.com. A 66.148.68.119 
 www.theshadowsembrace.com. CNAME theshadowsembrace.com.

After adding these records I reboot the entire server to be sure everything has restarted. No errors in the logs. I'll wait up to 24 hours and the nameservers still don't respond. If need be I'll post the zone and named.conf files. Anyone have an idea what I might be doing wrong? Unfortunately I have several domains sitting idle right now because I can't get this to work. :(
 
I have checked and found that bind is started on server:

$ telnet 66.148.68.119 53
Trying 66.148.68.119...
Connected to 66.148.68.119.
Escape character is '^]'.

Then I have tried to resolve this hostname directly by this nameserver:

$ host theshadowsembrace.com 66.148.68.119
Using domain server:
Name: 66.148.68.119
Address: 66.148.68.119#53
Aliases:

Host theshadowsembrace.com not found: 5(REFUSED)

Logs of named and zone file should be investigated on server. Try to resolve this domain directly on server with something like

# host theshadowsembrace.com localhost
 
Here is the zone file.

Code:
; *** This file is automatically generated by Plesk ***
$TTL    86400

@       IN      SOA     ns1.theshadowsembrace.com. eric\.n\.lowe.gmail.com. (
                        1268660221      ; Serial
                        3600    ; Refresh
                        3600    ; Retry
                        604800  ; Expire
                        10800 ) ; Minimum

theshadowsembrace.com.           IN NS   ns1.theshadowsembrace.com.
theshadowsembrace.com.           IN NS   ns2.theshadowsembrace.com.
theshadowsembrace.com.           IN A    66.148.68.119
webmail.theshadowsembrace.com.           IN A    66.148.68.119
mail.theshadowsembrace.com.              IN A    66.148.68.119
ns1.theshadowsembrace.com.               IN A    66.148.68.119
ns2.theshadowsembrace.com.               IN A    66.148.68.119
ftp.theshadowsembrace.com.               IN CNAME        theshadowsembrace.com.
www.theshadowsembrace.com.               IN CNAME        theshadowsembrace.com.
theshadowsembrace.com.           IN MX  10 mail.theshadowsembrace.com.
theshadowsembrace.com.           IN TXT  "v=spf1 +a +mx -all"

Here is the output of host theshadowsembrace.com localhost

Code:
Using domain server:
Name: localhost
Address: 127.0.0.1#53
Aliases: 

Host theshadowembrace.com not found: 3(NXDOMAIN)

Unless there is something I'm not aware of, the only log that I have with named entries is messages in /var/log

Here is the named entries in the log after stopping and starting named. The one where it states "the working directory is not writable" is an error I tried to rid myself of previously with no luck. All of the named folders and files have the proper owner and group, as well as rwe bits set. I can post those as well if need be.

Code:
Mar 17 16:02:12 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:12 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:12 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'ns2.aww-mud.org/AAAA/IN' denied
Mar 17 16:02:12 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'ns1.aww-mud.org/AAAA/IN' denied
Mar 17 16:02:12 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'ns2.aww-mud.org/AAAA/IN' denied
Mar 17 16:02:12 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'ns1.aww-mud.org/AAAA/IN' denied
Mar 17 16:02:16 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:16 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:16 sls-ec3p21 named[16149]: client 189.90.16.142#32769: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:16 sls-ec3p21 named[16149]: client 189.90.16.142#32769: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:20 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:20 sls-ec3p21 named[16149]: client 189.90.16.20#53: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:20 sls-ec3p21 named[16149]: client 189.90.16.142#32769: query (cache) 'aww-mud.org/MX/IN' denied
Mar 17 16:02:20 sls-ec3p21 named[16149]: shutting down: flushing changes
Mar 17 16:02:20 sls-ec3p21 named[16149]: stopping command channel on 127.0.0.1#953
Mar 17 16:02:20 sls-ec3p21 named[16149]: no longer listening on 127.0.0.1#53
Mar 17 16:02:20 sls-ec3p21 named[16149]: no longer listening on 66.148.68.119#53
Mar 17 16:02:20 sls-ec3p21 named[16149]: exiting
Mar 17 16:02:24 sls-ec3p21 named[4595]: starting BIND 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.1 -u named
Mar 17 16:02:24 sls-ec3p21 named[4595]: adjusted limit on open files from 1024 to 1048576
Mar 17 16:02:24 sls-ec3p21 named[4595]: found 1 CPU, using 1 worker thread
Mar 17 16:02:24 sls-ec3p21 named[4595]: using up to 4096 sockets
Mar 17 16:02:24 sls-ec3p21 named[4595]: loading configuration from '/etc/named.conf'
Mar 17 16:02:24 sls-ec3p21 named[4595]: using default UDP/IPv4 port range: [1024, 65535]
Mar 17 16:02:24 sls-ec3p21 named[4595]: using default UDP/IPv6 port range: [1024, 65535]
Mar 17 16:02:24 sls-ec3p21 named[4595]: listening on IPv4 interface lo, 127.0.0.1#53
Mar 17 16:02:24 sls-ec3p21 named[4595]: listening on IPv4 interface eth0, 66.148.68.119#53
Mar 17 16:02:24 sls-ec3p21 named[4595]: command channel listening on 127.0.0.1#953
Mar 17 16:02:24 sls-ec3p21 named[4595]: the working directory is not writable
Mar 17 16:02:24 sls-ec3p21 named[4595]: running

Thank you for your efforts in this matter.
 
Try to restart named and found in log that zone for theshadowsembrace.com was loaded without errors.
 
I apologize, but I don't understand if you're asking me to do something or making a statement.

You can contact support team if you are not familiar with Linux and can't perform my suggestions.
 
I'm quite familiar with Linux, but was not sure if you were asking me to do something or making a statement regarding what I had already done.

I've tail'd messages and posted the output prior to restarting named and right after restarting named.

Code:
[root@sls-ec3p21 log]# tail messages
Mar 22 05:23:25 sls-ec3p21 named[4595]: client 203.130.193.74#42016: query (cache) 'aww-mud.org/MX/IN' denied
Mar 22 05:23:25 sls-ec3p21 named[4595]: client 203.130.208.18#23974: query (cache) 'aww-mud.org/MX/IN' denied
Mar 22 05:23:25 sls-ec3p21 named[4595]: client 203.130.193.74#31111: query (cache) 'ns1.aww-mud.org/AAAA/IN' denied
Mar 22 05:23:25 sls-ec3p21 named[4595]: client 203.130.193.74#40867: query (cache) 'ns2.aww-mud.org/AAAA/IN' denied
Mar 22 05:23:25 sls-ec3p21 named[4595]: client 203.130.193.74#6318: query (cache) 'ns1.aww-mud.org/AAAA/IN' denied
Mar 22 05:23:25 sls-ec3p21 named[4595]: client 203.130.208.18#51685: query (cache) 'ns1.aww-mud.org/AAAA/IN' denied
Mar 22 05:23:25 sls-ec3p21 named[4595]: client 203.130.193.74#32706: query (cache) 'ns2.aww-mud.org/AAAA/IN' denied
Mar 22 05:23:26 sls-ec3p21 named[4595]: client 203.130.208.18#3392: query (cache) 'ns2.aww-mud.org/AAAA/IN' denied
Mar 22 05:23:26 sls-ec3p21 named[4595]: client 203.130.208.18#43797: query (cache) 'ns1.aww-mud.org/AAAA/IN' denied
Mar 22 05:23:26 sls-ec3p21 named[4595]: client 203.130.208.18#23382: query (cache) 'ns2.aww-mud.org/AAAA/IN' denied
[root@sls-ec3p21 log]# service named restart
Stopping named: .                                          [  OK  ]
Starting named:                                            [  OK  ]
[root@sls-ec3p21 log]# tail messages
Mar 22 05:26:08 sls-ec3p21 named[26137]: found 1 CPU, using 1 worker thread
Mar 22 05:26:08 sls-ec3p21 named[26137]: using up to 4096 sockets
Mar 22 05:26:08 sls-ec3p21 named[26137]: loading configuration from '/etc/named.conf'
Mar 22 05:26:08 sls-ec3p21 named[26137]: using default UDP/IPv4 port range: [1024, 65535]
Mar 22 05:26:08 sls-ec3p21 named[26137]: using default UDP/IPv6 port range: [1024, 65535]
Mar 22 05:26:08 sls-ec3p21 named[26137]: listening on IPv4 interface lo, 127.0.0.1#53
Mar 22 05:26:08 sls-ec3p21 named[26137]: listening on IPv4 interface eth0, 66.148.68.119#53
Mar 22 05:26:08 sls-ec3p21 named[26137]: command channel listening on 127.0.0.1#953
Mar 22 05:26:08 sls-ec3p21 named[26137]: the working directory is not writable
Mar 22 05:26:08 sls-ec3p21 named[26137]: running
 
Ok, I cleaned the messages before performing this so there wouldn't be too many returns from grep.

[root@sls-ec3p21 ~]# cd /var/log
[root@sls-ec3p21 log]# > messages
[root@sls-ec3p21 log]# service named restart
Stopping named: . [ OK ]
Starting named: [ OK ]
[root@sls-ec3p21 log]#

Waited approximately 30 minutes.

[root@sls-ec3p21 log]# grep 'theshadowsembrace.com' messages
Mar 23 05:10:27 sls-ec3p21 named[3898]: client 76.76.11.241#42016: query (cache) 'theshadowsembrace.com/ANY/IN' denied
Mar 23 05:10:28 sls-ec3p21 named[3898]: client 76.76.11.241#42016: query (cache) 'theshadowsembrace.com/SOA/IN' denied
Mar 23 05:10:28 sls-ec3p21 named[3898]: client 76.76.11.241#42016: query (cache) 'theshadowsembrace.com/A/IN' denied
Mar 23 05:10:28 sls-ec3p21 named[3898]: client 76.76.11.241#42016: query (cache) 'theshadowsembrace.com/MX/IN' denied
Mar 23 05:10:28 sls-ec3p21 named[3898]: client 76.76.11.241#42016: query (cache) 'www.theshadowsembrace.com/A/IN' denied
Mar 23 05:26:44 sls-ec3p21 named[4053]: client 204.194.63.129#55697: query (cache) 'theshadowsembrace.com/A/IN' denied
Mar 23 05:26:45 sls-ec3p21 named[4053]: client 204.194.60.10#54787: query (cache) 'theshadowsembrace.com/A/IN' denied
Mar 23 05:27:15 sls-ec3p21 named[4053]: client 204.194.63.129#21024: query (cache) 'www.theshadowsembrace.com/A/IN' denied
Mar 23 05:27:15 sls-ec3p21 named[4053]: client 204.194.63.129#21024: query (cache) 'www.theshadowsembrace.com/A/IN' denied
Mar 23 05:27:16 sls-ec3p21 named[4053]: client 204.194.60.10#64169: query (cache) 'www.theshadowsembrace.com/A/IN' denied
Mar 23 05:27:16 sls-ec3p21 named[4053]: client 204.194.60.10#64169: query (cache) 'www.theshadowsembrace.com/A/IN' denied
Mar 23 05:37:15 sls-ec3p21 named[4246]: client 204.194.63.129#35390: query (cache) 'theshadowsembrace.com/A/IN' denied
Mar 23 05:37:15 sls-ec3p21 named[4246]: client 204.194.60.10#59935: query (cache) 'theshadowsembrace.com/A/IN' denied
Mar 23 05:37:19 sls-ec3p21 named[4246]: client 204.194.63.129#55656: query (cache) 'www.theshadowsembrace.com/A/IN' denied
Mar 23 05:37:20 sls-ec3p21 named[4246]: client 204.194.60.10#52396: query (cache) 'www.theshadowsembrace.com/A/IN' denied
 
Name resolution

Eric,

Question 1: Are you a reseller or a partner or do you just use PLESK from a reseller service. I see your domain is hosted with ENOM.

Question 2: Do you know what HSPC or PBA is?
 
I have a root server that I use for hosting a few websites, games, and doing application development where the apps need to be available on the Internet. I'm not a reseller or anything of that nature.

That's odd about the domain. I have it currently registered through Superb Internet, who are the same people I get the server from. I've raised a ticket with them to see why it would have Enom listed as the registrar, but the domain was resolving properly until Superb upgraded me to Plesk 9.3.
 
Question 1: Are you a reseller or a partner or do you just use PLESK from a reseller service. I see your domain is hosted with ENOM.

I use Plesk as a front-end for a few friends and family to manage their domains on my dedicated root server, as well as the Internet apps and games that I develop. Superb is a reseller for eNom, thus my domains will say eNom, though I have them registered through Superb. I have a 100 domain license for Plesk for my root server.

Question 2: Do you know what HSPC or PBA is?
I am not familiar with these services. I do not use them on my root server.
 
Back
Top