I did a basic installation of Debian, which will be used for a mail server "ZIMBRA". I Installed the bind9 and did the configuration of the zones and created the files in the directory / etc / bind.
After the process I typed the following command to test my DNS:
nslookup mail.hotelpart.com and presented the following error:
![]()
**************************************************
* mail:/# nslookup mail.hotelpart.com *
* Server: 127.0.0.1 *
* Address: 127.0.0.1#53 *
* *
*** server can't find mail.hoteldofrade.com: SERVFAIL *
**************************************************
I would enlist the help of you to resolve this problem that I have some time I'm trying to solve:
Easier to stay I put my files in message: The files named.conf, db.hotelpart.com and db.111.20.11.200.
-------------------------------------------------------------------------
File named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
include "/etc/bind/named.conf.options";
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
zone "hotelpart.com"{
notify no;
type master;
file "/etc/bind/db.hotelpart.com";
};
zone "111.20.11.200.in-addr.arpa"{
notify no;
type master;
file "/etc/bind/db.111.20.11.200";
};
// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };
// From the release notes:
// Because many of our users are uncomfortable receiving undelegated answers
// from root or top level domains, other than a few for whom that behaviour
// has been trusted and expected for quite some length of time, we have now
// introduced the "root-delegations-only" feature which applies delegation-only
// logic to all top level domains, and to the root domain. An exception list
// should be specified, including "MUSEUM" and "DE", and any other top level
// domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };
include "/etc/bind/named.conf.local";
-------------------------------------------------------------------------
File db.hotelpart.com
;
; BIND data file for local loopback interface
;
$TTL 86400
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
1 ; Serial
3600 ; Refresh
86400 ; Retry
2419200 ; Expire
3600
)
;
@ IN NS localhost
@ IN MX 5 mail.hotelpart.com
localhost IN A 127.0.0.1
www IN A 200.11.20.111
mail IN A 200.11.20.111
-------------------------------------------------------------------------
File db.111.20.11.200
;
; BIND data file for local loopback interface
;
$TTL 86400
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN MX mail.hotelpart.com.
@ IN A 200.11.20.111
@ IN PTR mail.hotelpart.com.
Thanks!!!
I count on the help of you!!!![]()


LinkBack URL
About LinkBacks





)

