rdshosthing
11/03/10, 05:24
Hello, i have some troubles with setting up a nameserver in PLESK for months now. I have tried all possible scenario's but i can not get this to work.
I am really in need for some help, and if you can i will really appreciate it.
Basically what i want is to just set up a nameserver in PLESK. I have a primary IP, and my host gave me a secondary nameserver i can use. My host is leaseweb in the netherlands.
I have made some screenshots of the important parts in my opinion, maybe you guys can see some errors in them.
To use the secondary nameserver provided by leaseweb i had to enable ACL on that account, i did so and made a screenshot of that too.
The DNS recursion is set to localnets.
These settings have not changed for months, so the dns should be fully updated everywhere.
The check i run is the following:
https://www.sidn.nl/over-nl/aanvraag-abonnement/name-server-check/
Domeinnaam (inclusief .nl): rdshosting.nl
Eerste Nameserver: ns1.rdshosting.nl
Eerste IP: 62.212.66.33
Tweede Nameserver: ns7.leaseweb.net
Tweede ip: 62.212.76.50
If i run the dns check of the netherlands it gives me the following errors:
--------------------------
* primary name server "ns1.rdshosting.nl." Error: specified name server is not listed as NS record. All public name servers for a domain must also be listed as NS records in the zone of the domain. This domain was specified explicitly as a name server, but not found in the zone description of the primary name server. TE.6a
rdshosting.nl. 86400 IN SOA ns1.rdspartners.nl. saif2k.hotmail.com. (2010031102 12H 1H 7D 3H) Error: the MNAME in SOA says "ns1.rdspartners.nl." is the primary name server. The MNAME field in the SOA record (first parameter) lists a different primary name server from the one specified for this check. RFC1035 section 3.3.13
rdshosting.nl. 86400 IN NS ns1.rdspartners.nl. Warning: hidden name server "ns1.rdspartners.nl." never used for first contact. The zone contains an NS record for a host which is not in the list of specified name servers. Hence, this name server will not be used to initiate contact to the domain. It may be used in sequential lookups, so it may still be useful.
* secondary name server "ns1.rdspartners.nl." [BROKEN] [HIDDEN] Failure: name server at 77.232.85.129 cannot be reached: (unknown error) The name server could not be contacted, which may be due to temporary technical problems or global DNS configuration mistakes. The internal error is shown, but not always clear about the cause.
* secondary name server "ns7.leaseweb.net." Info: name server looks correctly configured.
-------------------------------------------
I have the content of the file etc/named.conf also:
// $Id: named.conf,v 1.1.1.1 2001/10/15 07:44:36 kap Exp $
//
// Refer to the named(8) man page for details. If you are ever going
// to setup a primary server, make sure you've understood the hairy
// details of how DNS is working. Even with simple mistakes, you can
// break connectivity for affected parties, or cause huge amount of
// useless Internet traffic.
options {
allow-recursion {
localnets;
};
directory "/var";
auth-nxdomain no;
pid-file "/var/run/named/named.pid";
// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
forwarders {
127.0.0.1;
};
*/
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
/*
* If running in a sandbox, you may have to specify a different
* location for the dumpfile.
*/
// dump-file "s/named_dump.db";
};
//Use with the following in named.conf, adjusting the allow list as needed:
key "rndc-key" {
algorithm hmac-md5;
secret "CeMgS23y0oWE20nyv0x40Q==";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
// Note: the following will be supported in a future release.
/*
host { any; } {
topology {
127.0.0.0/8;
};
};
*/
// Setting up secondaries is way easier and the rough picture for this
// is explained below.
//
// If you enable a local name server, don't forget to enter 127.0.0.1
// into your /etc/resolv.conf so this server will be queried first.
// Also, make sure to enable it in /etc/rc.conf.
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example secondary config entries. It can be convenient to become
// a secondary at least for the zone where your own domain is in. Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is the first bytes of the respective IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to setup a primary zone, better make sure you fully
// understand how DNS and BIND works, however. There are sometimes
// unobvious pitfalls. Setting up a secondary is comparably simpler.
//
// NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead.
//
// NOTE!!! FreeBSD runs bind in a sandbox (see named_flags in rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind. The following sequence is suggested:
//
// mkdir /etc/namedb/s
// chown bind.bind /etc/namedb/s
// chmod 750 /etc/namedb/s
zone "rdshosting.nl" {
type master;
file "rdshosting.nl";
allow-transfer {
77.232.85.129;
62.212.76.50;
common-allow-transfer;
};
};
zone "66.212.62.in-addr.arpa" {
type master;
file "66.212.62.in-addr.arpa";
allow-transfer {
common-allow-transfer;
};
};
acl common-allow-transfer {
62.212.76.50;
};
--------------------------------
As i mentioned i made some screenshots of some parts:
First the dns settings in plesk:
http://www.freeimagehosting.net/uploads/2480faed5e.jpg
Second the acl settings in plesk:
http://www.freeimagehosting.net/uploads/777f5e69b0.jpg
Third my settings at leaseweb:
http://www.freeimagehosting.net/uploads/de7122b19c.jpg
And last the secondary nameserver settings from leaseweb:
http://www.freeimagehosting.net/uploads/fd1da38a8f.jpg
------------------------------------------
If someone has anysuggestion at all on this this will be highly appriciated.
Thank you for your time!
PS. I am dutch so dutch answers are welcome aswell
I am really in need for some help, and if you can i will really appreciate it.
Basically what i want is to just set up a nameserver in PLESK. I have a primary IP, and my host gave me a secondary nameserver i can use. My host is leaseweb in the netherlands.
I have made some screenshots of the important parts in my opinion, maybe you guys can see some errors in them.
To use the secondary nameserver provided by leaseweb i had to enable ACL on that account, i did so and made a screenshot of that too.
The DNS recursion is set to localnets.
These settings have not changed for months, so the dns should be fully updated everywhere.
The check i run is the following:
https://www.sidn.nl/over-nl/aanvraag-abonnement/name-server-check/
Domeinnaam (inclusief .nl): rdshosting.nl
Eerste Nameserver: ns1.rdshosting.nl
Eerste IP: 62.212.66.33
Tweede Nameserver: ns7.leaseweb.net
Tweede ip: 62.212.76.50
If i run the dns check of the netherlands it gives me the following errors:
--------------------------
* primary name server "ns1.rdshosting.nl." Error: specified name server is not listed as NS record. All public name servers for a domain must also be listed as NS records in the zone of the domain. This domain was specified explicitly as a name server, but not found in the zone description of the primary name server. TE.6a
rdshosting.nl. 86400 IN SOA ns1.rdspartners.nl. saif2k.hotmail.com. (2010031102 12H 1H 7D 3H) Error: the MNAME in SOA says "ns1.rdspartners.nl." is the primary name server. The MNAME field in the SOA record (first parameter) lists a different primary name server from the one specified for this check. RFC1035 section 3.3.13
rdshosting.nl. 86400 IN NS ns1.rdspartners.nl. Warning: hidden name server "ns1.rdspartners.nl." never used for first contact. The zone contains an NS record for a host which is not in the list of specified name servers. Hence, this name server will not be used to initiate contact to the domain. It may be used in sequential lookups, so it may still be useful.
* secondary name server "ns1.rdspartners.nl." [BROKEN] [HIDDEN] Failure: name server at 77.232.85.129 cannot be reached: (unknown error) The name server could not be contacted, which may be due to temporary technical problems or global DNS configuration mistakes. The internal error is shown, but not always clear about the cause.
* secondary name server "ns7.leaseweb.net." Info: name server looks correctly configured.
-------------------------------------------
I have the content of the file etc/named.conf also:
// $Id: named.conf,v 1.1.1.1 2001/10/15 07:44:36 kap Exp $
//
// Refer to the named(8) man page for details. If you are ever going
// to setup a primary server, make sure you've understood the hairy
// details of how DNS is working. Even with simple mistakes, you can
// break connectivity for affected parties, or cause huge amount of
// useless Internet traffic.
options {
allow-recursion {
localnets;
};
directory "/var";
auth-nxdomain no;
pid-file "/var/run/named/named.pid";
// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
forwarders {
127.0.0.1;
};
*/
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
/*
* If running in a sandbox, you may have to specify a different
* location for the dumpfile.
*/
// dump-file "s/named_dump.db";
};
//Use with the following in named.conf, adjusting the allow list as needed:
key "rndc-key" {
algorithm hmac-md5;
secret "CeMgS23y0oWE20nyv0x40Q==";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
// Note: the following will be supported in a future release.
/*
host { any; } {
topology {
127.0.0.0/8;
};
};
*/
// Setting up secondaries is way easier and the rough picture for this
// is explained below.
//
// If you enable a local name server, don't forget to enter 127.0.0.1
// into your /etc/resolv.conf so this server will be queried first.
// Also, make sure to enable it in /etc/rc.conf.
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example secondary config entries. It can be convenient to become
// a secondary at least for the zone where your own domain is in. Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is the first bytes of the respective IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to setup a primary zone, better make sure you fully
// understand how DNS and BIND works, however. There are sometimes
// unobvious pitfalls. Setting up a secondary is comparably simpler.
//
// NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead.
//
// NOTE!!! FreeBSD runs bind in a sandbox (see named_flags in rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind. The following sequence is suggested:
//
// mkdir /etc/namedb/s
// chown bind.bind /etc/namedb/s
// chmod 750 /etc/namedb/s
zone "rdshosting.nl" {
type master;
file "rdshosting.nl";
allow-transfer {
77.232.85.129;
62.212.76.50;
common-allow-transfer;
};
};
zone "66.212.62.in-addr.arpa" {
type master;
file "66.212.62.in-addr.arpa";
allow-transfer {
common-allow-transfer;
};
};
acl common-allow-transfer {
62.212.76.50;
};
--------------------------------
As i mentioned i made some screenshots of some parts:
First the dns settings in plesk:
http://www.freeimagehosting.net/uploads/2480faed5e.jpg
Second the acl settings in plesk:
http://www.freeimagehosting.net/uploads/777f5e69b0.jpg
Third my settings at leaseweb:
http://www.freeimagehosting.net/uploads/de7122b19c.jpg
And last the secondary nameserver settings from leaseweb:
http://www.freeimagehosting.net/uploads/fd1da38a8f.jpg
------------------------------------------
If someone has anysuggestion at all on this this will be highly appriciated.
Thank you for your time!
PS. I am dutch so dutch answers are welcome aswell