LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 04-01-2009, 04:07 PM   #1
jcvalim
Member
 
Registered: Apr 2009
Location: Brazil
Distribution: Debian
Posts: 47

Rep: Reputation: 15
Exclamation DNS SERVER WITH ERROR: "Server Can't Find : SERVFAIL"


I did a basic installation of Debian, which will be used for a mail server. 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.hotelpart.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!!!

Last edited by jcvalim; 04-02-2009 at 09:28 AM.
 
Old 04-02-2009, 08:34 AM   #2
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Quote:
* mail:/# nslookup mail.hotelpart.com *
* Server: 127.0.0.1 *
* Address: 127.0.0.1#53 *
* *
*** server can't find mail.hoteldofrade.com: SERVFAIL *
You are looking for mail.hotelpart.com and get a response from your server for mail.hoteldofrade.com!!!! Does mail.hoteldofrade.com looks familiar to you?
 
Old 04-02-2009, 09:34 AM   #3
jcvalim
Member
 
Registered: Apr 2009
Location: Brazil
Distribution: Debian
Posts: 47

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by bathory View Post
You are looking for mail.hotelpart.com and get a response from your server for mail.hoteldofrade.com!!!! Does mail.hoteldofrade.com looks familiar to you?
Sorry, The domain correct is mail.hotelpart.com. I did commit a mistake.

mail:~# nslookup mail.hotelpart.com
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find mail.hotelpart.com: SERVFAIL
 
Old 04-02-2009, 09:40 AM   #4
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
That's OK.
Change
Quote:
@ IN NS localhost
to
Code:
 IN NS mail.hotelpart.com.
increase the serial and reload named.
You need to do the same in the reverse zone too, as you don't have any NS record.
 
Old 04-02-2009, 09:54 AM   #5
jcvalim
Member
 
Registered: Apr 2009
Location: Brazil
Distribution: Debian
Posts: 47

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by bathory View Post
That's OK.
Change
to
Code:
 IN NS mail.hotelpart.com.
increase the serial and reload named.
You need to do the same in the reverse zone too, as you don't have any NS record.
I did what you told me to do, but there still remains the problem!!!

mail:/etc/bind# nslookup mail.hotelpart.com
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find mail.hotelpart.com: SERVFAIL

Do You have more any tips, for help me ?????

Last edited by jcvalim; 04-02-2009 at 10:09 AM.
 
Old 04-02-2009, 11:38 AM   #6
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Could you please post the output of the commands
Code:
ps -ef|grep named
named-checkconf -z
and the relevant lines from /var/log/messages, or /var/log/syslog (whatever file named writes its logs), when you restart named.
Also since I don't use debian, what's in /etc/bind/named.conf.options and /etc/bind/named.conf.local
 
Old 04-02-2009, 12:07 PM   #7
jcvalim
Member
 
Registered: Apr 2009
Location: Brazil
Distribution: Debian
Posts: 47

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by bathory View Post
Could you please post the output of the commands
Code:
ps -ef|grep named
named-checkconf -z
and the relevant lines from /var/log/messages, or /var/log/syslog (whatever file named writes its logs), when you restart named.
Also since I don't use debian, what's in /etc/bind/named.conf.options and /etc/bind/named.conf.local
mail:~# ps -ef|grep named
bind 6082 1 0 08:56 ? 00:00:00 /usr/sbin/named -u bind
root 6184 6178 0 11:00 pts/2 00:00:00 grep named
mail:~# named-checkconf -z
zone localhost/IN: loaded serial 1
zone 127.in-addr.arpa/IN: loaded serial 1
zone 0.in-addr.arpa/IN: loaded serial 1
zone 255.in-addr.arpa/IN: loaded serial 1
/etc/bind/db.hotelpart.com:4: no current owner name
/etc/bind/db.hotelpart.com:5: no current owner name
/etc/bind/db.hotelpart.com:13: no current owner name
/etc/bind/db.hotelpart.com:14: no current owner name
/etc/bind/db.hotelpart.com:15: no current owner name
/etc/bind/db.hotelpart.com:16: no current owner name
/etc/bind/db.hotelpart.com:17: no current owner name
zone hotelpart.com/IN: loading master file /etc/bind/db.hotelpart.com: no owner
_default/hotelpart.com/IN: no owner
/etc/bind/db.111.20.11.200:4: no current owner name
/etc/bind/db.111.20.11.200:5: no current owner name
/etc/bind/db.111.20.11.200:12: no current owner name
/etc/bind/db.111.20.11.200:13: no current owner name
/etc/bind/db.111.20.11.200:14: no current owner name
/etc/bind/db.111.20.11.200:15: no current owner name
zone 111.20.11.200.in-addr.arpa/IN: loading master file /etc/bind/db.111.20.11.200: no owner
_default/111.20.11.200.in-addr.arpa/IN: no owner


File /var/log/syslog

Apr 2 06:25:09 mail syslogd 1.4.1#18: restart.
Apr 2 06:43:00 mail -- MARK --
Apr 2 07:03:00 mail -- MARK --
Apr 2 07:17:01 mail /USR/SBIN/CRON[6026]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 2 07:43:01 mail -- MARK --
Apr 2 08:03:01 mail -- MARK --
Apr 2 08:17:01 mail /USR/SBIN/CRON[6040]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 2 08:43:01 mail -- MARK --
Apr 2 08:56:17 mail named[2490]: shutting down: flushing changes
Apr 2 08:56:17 mail named[2490]: stopping command channel on 127.0.0.1#953
Apr 2 08:56:17 mail named[2490]: stopping command channel on ::1#953
Apr 2 08:56:17 mail named[2490]: no longer listening on ::#53
Apr 2 08:56:17 mail named[2490]: no longer listening on 127.0.0.1#53
Apr 2 08:56:17 mail named[2490]: no longer listening on 10.0.0.250#53
Apr 2 08:56:17 mail named[2490]: no longer listening on 200.11.20.111#53
Apr 2 08:56:17 mail named[2490]: exiting
Apr 2 08:56:19 mail named[6082]: starting BIND 9.3.4-P1.1 -u bind
Apr 2 08:56:19 mail named[6082]: found 1 CPU, using 1 worker thread
Apr 2 08:56:19 mail named[6082]: loading configuration from '/etc/bind/named.conf'
Apr 2 08:56:19 mail named[6082]: listening on IPv6 interfaces, port 53
Apr 2 08:56:19 mail named[6082]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 2 08:56:19 mail named[6082]: listening on IPv4 interface eth1, 10.0.0.250#53
Apr 2 08:56:19 mail named[6082]: listening on IPv4 interface eth0, 200.11.20.111#53
Apr 2 08:56:19 mail named[6082]: command channel listening on 127.0.0.1#953
Apr 2 08:56:19 mail named[6082]: command channel listening on ::1#953
Apr 2 08:56:19 mail named[6082]: zone 0.in-addr.arpa/IN: loaded serial 1
Apr 2 08:56:19 mail named[6082]: zone 127.in-addr.arpa/IN: loaded serial 1
Apr 2 08:56:19 mail named[6082]: /etc/bind/db.111.20.11.200:4: no current owner name
Apr 2 08:56:19 mail named[6082]: zone 111.20.11.200.in-addr.arpa/IN: loading master file /etc/bind/db.111.20.11.200: no owner
Apr 2 08:56:19 mail named[6082]: zone 255.in-addr.arpa/IN: loaded serial 1
Apr 2 08:56:19 mail named[6082]: /etc/bind/db.hotelpart.com:4: no current owner name
Apr 2 08:56:19 mail named[6082]: zone hotelpart.com/IN: loading master file /etc/bind/db.hotelpart.com: no owner
Apr 2 08:56:19 mail named[6082]: zone localhost/IN: loaded serial 1
Apr 2 08:56:19 mail named[6082]: running
Apr 2 09:17:01 mail /USR/SBIN/CRON[6096]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 2 09:43:02 mail -- MARK --
Apr 2 10:03:02 mail -- MARK --
Apr 2 10:11:49 mail named[6082]: lame server resolving 'www.estadosp.com.br' (in 'estadosp.com.br'?): 72.233.50.75#53
Apr 2 10:11:49 mail named[6082]: lame server resolving 'www.estadosp.com.br' (in 'estadosp.com.br'?): 72.233.50.76#53
Apr 2 10:17:01 mail /USR/SBIN/CRON[6133]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 2 10:43:03 mail -- MARK --
Apr 2 11:03:03 mail -- MARK --

--------------------------------------------------------------

/etc/bind/named.conf.options

options {
directory "/var/cache/bind";

// 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 and later use an unprivileged
// port by default.

// query-source address * port 53;

// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.

// forwarders {
// 0.0.0.0;
// };

auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
};

----------------------------------------------------------------

File /etc/bind/named.conf.local

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";


Thanks!!!
 
Old 04-02-2009, 01:12 PM   #8
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
How do you edit the zone files? I guess there are some non printable characters somewhere that are making this mess. Open /etc/bind/db.hotelpart.com with vi and check for special characters, or use (copy/paste) the following in a new file (keep a backup of the original just in case):
Code:
$TTL 86400
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
10 ; Serial
3600 ; Refresh
86400 ; Retry
2419200 ; Expire
3600 )
;
 IN NS mail.hotelpart.com.
 IN MX 5 mail.hotelpart.com.
localhost. IN A 127.0.0.1
www.hotelpart.com. IN A 200.11.20.111
mail.hotelpart.com. IN A 200.11.20.111
Note: I've increased serial to 10. If you have done more that 10 edits, then change it accordingly
 
Old 04-02-2009, 02:10 PM   #9
jcvalim
Member
 
Registered: Apr 2009
Location: Brazil
Distribution: Debian
Posts: 47

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by bathory View Post
How do you edit the zone files? I guess there are some non printable characters somewhere that are making this mess. Open /etc/bind/db.hotelpart.com with vi and check for special characters, or use (copy/paste) the following in a new file (keep a backup of the original just in case):
Code:
$TTL 86400
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
10 ; Serial
3600 ; Refresh
86400 ; Retry
2419200 ; Expire
3600 )
;
 IN NS mail.hotelpart.com.
 IN MX 5 mail.hotelpart.com.
localhost. IN A 127.0.0.1
www.hotelpart.com. IN A 200.11.20.111
mail.hotelpart.com. IN A 200.11.20.111
Note: I've increased serial to 10. If you have done more that 10 edits, then change it accordingly

I managed to solve one problem, now tell me if this is normal????

mail:~# nslookup mail.hotelpart.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: mail.hotelpart.com
Address: 200.11.20.111

mail:~# nslookup 200.11.20.111
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find 111.20.11.200.in-addr.arpa: SERVFAIL

I still have something wrong with my DNS!!!

I hope I can count on your help!!!

Last edited by jcvalim; 04-02-2009 at 02:11 PM.
 
Old 04-02-2009, 02:15 PM   #10
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
How did you managed to solve the problem?
You should do the same for the reverse zone.

Last edited by bathory; 04-02-2009 at 05:27 PM.
 
Old 04-02-2009, 03:45 PM   #11
jcvalim
Member
 
Registered: Apr 2009
Location: Brazil
Distribution: Debian
Posts: 47

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by bathory View Post
How did you managed to solve the problem?
You should use the same for the reverse zone.
I made some changes in my files: db.hotelpart.com and db.111.20.11.200.
But but the change only works for db.hotelpart.com file.

Below are the current files:

File db.hotelpart.com

$TTL 86400
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
1 ; Serial
3600 ; Refresh
86400 ; Retry
2419200 ; Expire
3600
)
@ IN NS mail.hotelpart.com.
@ IN MX 5 mail.hotelpart.com.
localhost IN A 127.0.0.1
www IN A 201.11.14.114
mail IN A 200.11.20.111


File db.111.20.11.200

$TTL 86400
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
@ IN NS mail.hotelpart.com.
@ IN MX mail.hotelpart.com.
@ IN A 200.11.20.111
@ IN PTR mail.hotelpart.com.


Is probably missing some detail, but I didn't identify... I need your help.

Thanks
 
Old 04-02-2009, 04:55 PM   #12
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Could you be more specific about what changes you've done, because to me both files look the same, apart from the NS record and a missing dot "." at the MX record.
Check syslog to see if you still get the same "no owner" error, so we will know if it's the same problem, or something else.
You should also note, that reverse dns is more tricky. If you have given a chunk of a /24 subnet from your isp, you should contact them to make sure that they have given you the delegation of that chunk. Then you must use in named.conf a zone name that mtches this chunk (something like xx/yy.20.11.200.in-addr.arpa, where xx is the first IP and yy the subnet mask). The reverse zone file you've posted will work only if you own the whole 200.11.20.0/24 subnet. Not to mention that for www you have an IP of 201.11.14.114 (that belongs to a different subnet: 201.11.14.0/24)

In the zone file you should use:
Code:
$TTL 86400
$ORIGIN xx/yy.20.11.200.in-addr.arpa.
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
@ IN NS mail.hotelpart.com.
@ IN MX mail.hotelpart.com.

111 IN PTR mail.hotelpart.com.
Take a look here for the Classless IN-ADDR.ARPA delegation.
 
Old 04-03-2009, 09:48 AM   #13
jcvalim
Member
 
Registered: Apr 2009
Location: Brazil
Distribution: Debian
Posts: 47

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by bathory View Post
Could you be more specific about what changes you've done, because to me both files look the same, apart from the NS record and a missing dot "." at the MX record.
Check syslog to see if you still get the same "no owner" error, so we will know if it's the same problem, or something else.
You should also note, that reverse dns is more tricky. If you have given a chunk of a /24 subnet from your isp, you should contact them to make sure that they have given you the delegation of that chunk. Then you must use in named.conf a zone name that mtches this chunk (something like xx/yy.20.11.200.in-addr.arpa, where xx is the first IP and yy the subnet mask). The reverse zone file you've posted will work only if you own the whole 200.11.20.0/24 subnet. Not to mention that for www you have an IP of 201.11.14.114 (that belongs to a different subnet: 201.11.14.0/24)

In the zone file you should use:
Code:
$TTL 86400
$ORIGIN xx/yy.20.11.200.in-addr.arpa.
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
@ IN NS mail.hotelpart.com.
@ IN MX mail.hotelpart.com.

111 IN PTR mail.hotelpart.com.
Take a look here for the Classless IN-ADDR.ARPA delegation.
I didn't understand the right information that you spoke.
I made the changes mentioned by you, but I do not know if it was to be done this way because I have never seen any documentation talking about this type of reverse zone.

Here are my new files: db.111.20.11.200 and syslog:

$TTL 86400
$ORIGIN 11/29.20.11.200.in-addr.arpa.
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
@ IN NS mail.hotelpart.com.
@ IN MX mail.hotelpart.com.
@ IN A 200.11.20.111
@ IN PTR mail.hotelpart.com.
111 IN PTR mail.hotelpart.com.

mail:~# nslookup 200.11.20.111
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find 111.20.11.200.in-addr.arpa: SERVFAIL

Thanks.
 
Old 04-03-2009, 09:54 AM   #14
jcvalim
Member
 
Registered: Apr 2009
Location: Brazil
Distribution: Debian
Posts: 47

Original Poster
Rep: Reputation: 15
My log is very big, I can not to post. Sorry!!!

Last edited by jcvalim; 04-03-2009 at 09:59 AM.
 
Old 04-03-2009, 11:11 AM   #15
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Quote:
Here are my new files: db.111.20.11.200 and syslog:

$TTL 86400
$ORIGIN 11/29.20.11.200.in-addr.arpa.
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
So you're delegating the 200.11.20.XXX/29 subnet. Please verify with your ISP the last octet of the starting IP, because if my calculations are correct 200.11.20.111 is the broadcast address (that cannot be assigned to a host)
Your IP range is probably 200.11.20.105-200.11.20.111.
If that's correct change the in-addr.arpa zone name to 105/29.20.11.200.in-addr.arpa. in named.conf and then change the db.111.20.11.200 file like this:
Code:
$TTL 86400
$ORIGIN 105/29.20.11.200.in-addr.arpa.
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
2 ; Serial Must be increased after every change
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
 IN NS mail.hotelpart.com.
 IN MX mail.hotelpart.com.

111 IN PTR mail.hotelpart.com.
Regarding the logs, you should post only those after reloading named.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
anybody familiar with this error "Xlib: connection to ":0.0" refused by server" ? rajnivanza Linux - Newbie 3 03-22-2009 05:10 PM
Attempt to connect to Cups server."Server Error" richag77 Linux - Newbie 3 02-25-2008 07:31 AM
"Fatal server error. Caught signal 11, server aborting" please help ! Fear58 Linux - General 2 10-16-2007 10:33 PM
Apache Alias Returns 404 or "Cannot find server or DNS Error" The00Dustin Linux - Software 3 02-14-2006 12:44 PM
dns & apache server "need help installing" faustozabdi Linux - Software 1 01-03-2006 04:46 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 02:49 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration