DNS SERVER WITH ERROR: "Server Can't Find : SERVFAIL"

jcvalim · 04-03-2009, 12:41 PM

Quote:

Originally Posted by bathory

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.

After the change was this:

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: NXDOMAIN

But after some tests I still say that:

Checking the reverse DNS of the IP [200.11.20.111]:

$ host 200.11.20.111
Host 111.20.11.200.in-addr.arpa not found: 3(NXDOMAIN)

The DNS of the IP [200.11.20.111] is not properly configured.

What do you think that?

bathory · 04-03-2009, 03:48 PM

I think that this is because the 200.11.20.111 is not a valid IP for a host as it's the subnet broadcast address. Of course this is based on my calculations after seeing that "/29" subnet mask in your zone name. Thus I cannot be sure that the zone file I gave you is right. Alt least you get rid of the SERVFAIL error.
If you don't know the IP range of your subnet, you have to ask you ISP for the correct range. You cannot just use IPs and expect them to work.
Meanwhile you can try to add another record and see it that works:

Code:

$TTL 86400
$ORIGIN 105/29.20.11.200.in-addr.arpa.
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
3 ; 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. ;broken?
110 IN PTR test.hotelpart.com.

Once again contact your ISP if you don't know the IP range of your network.

jcvalim · 04-06-2009, 07:02 AM

Quote:

Originally Posted by bathory

I think that this is because the 200.11.20.111 is not a valid IP for a host as it's the subnet broadcast address. Of course this is based on my calculations after seeing that "/29" subnet mask in your zone name. Thus I cannot be sure that the zone file I gave you is right. Alt least you get rid of the SERVFAIL error.
If you don't know the IP range of your subnet, you have to ask you ISP for the correct range. You cannot just use IPs and expect them to work.
Meanwhile you can try to add another record and see it that works:

Code:

$TTL 86400
$ORIGIN 105/29.20.11.200.in-addr.arpa.
@ IN SOA mail.hotelpart.com. root.hotelpart.com. (
3 ; 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. ;broken?
110 IN PTR test.hotelpart.com.

Once again contact your ISP if you don't know the IP range of your network.

I made a change in my IP address. Now I'm using the IP xxx.xx.xx.xxx/29, but there still with the same problem.

File db.xxx.xx.xx.xxx

$TTL 86400
$ORIGIN 113/29.xx.xx.xxx.in-addr.arpa.
@ IN SOA mail.maydomain.com. root.maydomain.com. (
1 ; Serial Must be increased after every change
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
@ IN NS mail.mydomain.com.
@ IN MX mail.mydomain.com.
@ IN A xxx.xx.xx.xxx
118 IN PTR mail.mydomain.com.

bathory · 04-06-2009, 08:16 AM

Now you have changed completely subnet.
Anyway did you add the 113/29.17.18.201.in-addr.arpa. zone in named.conf?
Did you update the forward zone with the new ip of your NS (mail.hotelpart.com)?
What is the error you get now? Is it NXDOMAIN or SERVFAIL?

jcvalim · 04-06-2009, 08:48 AM

Quote:

Originally Posted by bathory

Now you have changed completely subnet.
Anyway did you add the 113/29.17.18.201.in-addr.arpa. zone in named.conf?
Did you update the forward zone with the new ip of your NS (mail.hotelpart.com)?
What is the error you get now? Is it NXDOMAIN or SERVFAIL?

do you have MSN because i would be better for I move the settings, to be exposed in the forum.

bathory · 04-06-2009, 09:01 AM

I don't have msn or any other IM. If you want you can pm me and I'll try to answer.
Anyway you can change the IPs and the domain using xx.xx.xx.xx and domain.com, if you don't feel comfortable using real data.

jcvalim · 04-06-2009, 09:18 AM

Quote:

Originally Posted by bathory

I don't have msn or any other IM. If you want you can pm me and I'll try to answer.
Anyway you can change the IPs and the domain using xx.xx.xx.xx and domain.com, if you don't feel comfortable using real data.

ok. I go do this so if you do not bother... Thanks. Do you may change your previous comment not to expose my IP address. I thank you.
I still continue with the message of NXDOMAIN. which file you need that I post here.

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

Name: mail.mydomain.com
Address: xxx.xx.xx.xxx
mail:/etc/bind# nslookup xxx.xx.xx.xxx
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find xxx.xx.xx.xxx.in-addr.arpa: NXDOMAIN

Thanks.

bathory · 04-06-2009, 09:37 AM

Have you increase the serial in the zone file (db.xxx.xx.xx.xxx)?
Do you see the changed serial when you reload the zone or bind?

jcvalim · 04-06-2009, 09:50 AM

Quote:

Originally Posted by bathory

Have you increase the serial in the zone file (db.xxx.xx.xx.xxx)?
Do you see the changed serial when you reload the zone or bind?

What should I do? What do you suggest?

I made all changes in the files: named.conf, db.mydomain.com, db.xxx.xx.xx.xxx

bathory · 04-06-2009, 10:33 AM

The changes do not take effect if you don't increase the serial number. Only then bind knows that it must re-read the zone as there are changes.
You could use this db.xx.xx.xx.xx

Code:

$TTL 86400
$ORIGIN 113/29.xx.xx.xxx.in-addr.arpa.
@ IN SOA mail.maydomain.com. root.maydomain.com. (
10 ; Serial Must be increased after every change
28800  ; Refresh
7200 ; Retry
604800 ; Expire
86400 ) ; Negative Cache TTL
 IN NS mail.mydomain.com.
 IN MX mail.mydomain.com.

118 IN PTR mail.mydomain.com.

Make sure that in the forward zone (db.mydomain.com) you have changed the IP of your dns (that is mail.mydomain.com) to the new IP:

Quote:

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

mail IN A xx.xx.xx.118

Post also the relevant part of syslog when you reload bind and the output of:

Code:

named-checkzone -d 113/29.xx.xx.xxx.in-addr.arpa. /path/to/db.xx.xx.xx

jcvalim · 04-06-2009, 12:17 PM

Quote:

Originally Posted by bathory

The changes do not take effect if you don't increase the serial number. Only then bind knows that it must re-read the zone as there are changes.
You could use this db.xx.xx.xx.xx

Code:

$TTL 86400
$ORIGIN 113/29.xx.xx.xxx.in-addr.arpa.
@ IN SOA mail.maydomain.com. root.maydomain.com. (
10 ; Serial Must be increased after every change
28800  ; Refresh
7200 ; Retry
604800 ; Expire
86400 ) ; Negative Cache TTL
 IN NS mail.mydomain.com.
 IN MX mail.mydomain.com.

118 IN PTR mail.mydomain.com.

Make sure that in the forward zone (db.mydomain.com) you have changed the IP of your dns (that is mail.mydomain.com) to the new IP:

Post also the relevant part of syslog when you reload bind and the output of:

Code:

named-checkzone -d 113/29.xx.xx.xxx.in-addr.arpa. /path/to/db.xx.xx.xx

I did everything as you asked me and gave this message:

mail:/# named-checkzone -d 113/29.xx.xx.xxx.in-addr.arpa. /path/to/db.118.xx.xx.xxx
loading "113/29.xx.xx.xxx.in-addr.arpa." from "/path/to/db.118.xx.xx.xxx" class "IN"
zone 113/29.xx.xx.xxx.in-addr.arpa/IN: loading master file /path/to/db.118.xx.xx.xxx: file not found

What does that mean?

bathory · 04-06-2009, 12:43 PM

You are supposed to replace /path/to/db/xx.xx.xx.xx with the actual path to the zone file. It should be /etc/bind/db.xx.xx.xx (from post #7).
Another one command to run is

Code:

nslookup mail.mydomain.com

to see if your dns is resolving.
Also don't forget to post the contents of syslog when you reload named.

jcvalim · 04-06-2009, 01:00 PM

Quote:

Originally Posted by bathory

You are supposed to replace /path/to/db/xx.xx.xx.xx with the actual path to the zone file. It should be /etc/bind/db.xx.xx.xx (from post #7).
Another one command to run is

Code:

nslookup mail.mydomain.com

to see if your dns is resolving.
Also don't forget to post the contents of syslog when you reload named.

Result:

mail:/# named-checkzone -d 113/29.17.18.201.in-addr.arpa. /etc/bind/db.118.xx.xx.xxx
loading "113/29.xx.xx.xxx.in-addr.arpa." from "/etc/bind/db.118.xx.xx.xxx" class "IN"
/etc/bind/db.118.xx.xx.xxx:10: 113/29.xx.xx.xxx.in-addr.arpa: bad owner name (check-names)
dns_rdata_fromtext: /etc/bind/db.118.xx.xx.xxx:10: near 'mail.mydomain.com.': not a valid number
zone 113/29.xx.xx.xxx.in-addr.arpa/IN: loading master file /etc/bind/db.118.xx.xx.xxx: not a valid number

===================================================

mail:/# nslookup mail.mydomain.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: mail.mydomain.com
Address: xxx.xx.xx.118

mail:/# nslookup xxx.xx.xx.118
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find 118.xx.xx.xxx.in-addr.arpa: NXDOMAIN

===================================================

syslog:

Apr 6 07:33:05 mail named[2482]: starting BIND 9.3.4-P1.1 -u bind
Apr 6 07:33:05 mail named[2482]: found 1 CPU, using 1 worker thread
Apr 6 07:33:05 mail named[2482]: loading configuration from '/etc/bind/named.conf'
Apr 6 07:33:05 mail named[2482]: listening on IPv6 interfaces, port 53
Apr 6 07:33:05 mail named[2482]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 6 07:33:05 mail named[2482]: listening on IPv4 interface eth1, 10.0.0.250#53
Apr 6 07:33:05 mail named[2482]: listening on IPv4 interface eth0, xxx.xx.xx.118#53
Apr 6 07:33:05 mail named[2482]: command channel listening on 127.0.0.1#953
Apr 6 07:33:05 mail named[2482]: command channel listening on ::1#953
Apr 6 07:33:05 mail named[2482]: zone 0.in-addr.arpa/IN: loaded serial 1
Apr 6 07:33:05 mail named[2482]: zone 127.in-addr.arpa/IN: loaded serial 1
Apr 6 07:33:05 mail named[2482]: /etc/bind/db.118.xx.xx.xxx:10: 113/29.xx.xx.xxx.in-addr.arpa: bad owner name (check-names)
Apr 6 07:33:05 mail named[2482]: zone 113/29.xx.xx.xxx.in-addr.arpa/IN: loading master file /etc/bind/db.118.xx.xx.xxx: bad owner name (check-names)
Apr 6 07:33:05 mail named[2482]: zone 255.in-addr.arpa/IN: loaded serial 1
Apr 6 07:33:05 mail named[2482]: zone mydomain.com/IN: loaded serial 1
Apr 6 07:33:05 mail named[2482]: zone localhost/IN: loaded serial 1
Apr 6 07:33:05 mail named[2482]: running
Apr 6 07:46:42 mail named[2482]: shutting down: flushing changes
Apr 6 07:46:42 mail named[2482]: stopping command channel on 127.0.0.1#953
Apr 6 07:46:42 mail named[2482]: stopping command channel on ::1#953
Apr 6 07:46:42 mail named[2482]: no longer listening on ::#53
Apr 6 07:46:42 mail named[2482]: no longer listening on 127.0.0.1#53
Apr 6 07:46:42 mail named[2482]: no longer listening on 10.0.0.250#53
Apr 6 07:46:42 mail named[2482]: no longer listening on xxx.xx.xx.118#53
Apr 6 07:46:42 mail named[2482]: exiting
Apr 6 07:46:44 mail named[2521]: starting BIND 9.3.4-P1.1 -u bind
Apr 6 07:46:44 mail named[2521]: found 1 CPU, using 1 worker thread
Apr 6 07:46:44 mail named[2521]: loading configuration from '/etc/bind/named.conf'
Apr 6 07:46:44 mail named[2521]: listening on IPv6 interfaces, port 53
Apr 6 07:46:44 mail named[2521]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 6 07:46:44 mail named[2521]: listening on IPv4 interface eth1, 10.0.0.250#53
Apr 6 07:46:44 mail named[2521]: listening on IPv4 interface eth0, xxx.xx.xx.118#53
Apr 6 07:46:44 mail named[2521]: command channel listening on 127.0.0.1#953
Apr 6 07:46:44 mail named[2521]: command channel listening on ::1#953
Apr 6 07:46:44 mail named[2521]: zone 0.in-addr.arpa/IN: loaded serial 1
Apr 6 07:46:44 mail named[2521]: dns_rdata_fromtext: /etc/bind/db.0.0.10:9: near 'mail.mydomain.com.': not a valid number
Apr 6 07:46:44 mail named[2521]: zone 0.0.10.in-addr.arpa/IN: loading master file /etc/bind/db.0.0.10: not a valid number
Apr 6 07:46:44 mail named[2521]: zone 127.in-addr.arpa/IN: loaded serial 1
Apr 6 07:46:44 mail named[2521]: /etc/bind/db.118.xx.xx.xxx:10: 113/29.xx.xx.xxx.in-addr.arpa: bad owner name (check-names)
Apr 6 07:46:44 mail named[2521]: zone 113/29.xx.xx.xxx.in-addr.arpa/IN: loading master file /etc/bind/db.118.xx.xx.xxx: bad owner name (check-names)
Apr 6 07:46:44 mail named[2521]: zone 255.in-addr.arpa/IN: loaded serial 1
Apr 6 07:46:44 mail named[2521]: zone mydomain.com/IN: loaded serial 1
Apr 6 07:46:44 mail named[2521]: zone localhost/IN: loaded serial 1
Apr 6 07:46:44 mail named[2521]: running
Apr 6 07:50:20 mail named[2521]: unexpected RCODE (SERVFAIL) resolving 'tslt.terra.com.mx/A/IN': 208.70.190.28#53
Apr 6 07:50:20 mail named[2521]: unexpected RCODE (SERVFAIL) resolving 'tslt.terra.com.mx/A/IN': 208.70.190.29#53
Apr 6 07:58:01 mail named[2521]: shutting down: flushing changes
Apr 6 07:58:01 mail named[2521]: stopping command channel on 127.0.0.1#953
Apr 6 07:58:01 mail named[2521]: stopping command channel on ::1#953
Apr 6 07:58:01 mail named[2521]: no longer listening on ::#53
Apr 6 07:58:01 mail named[2521]: no longer listening on 127.0.0.1#53
Apr 6 07:58:01 mail named[2521]: no longer listening on 10.0.0.250#53
Apr 6 07:58:01 mail named[2521]: no longer listening on xxx.xx.xx.118#53
Apr 6 07:58:01 mail named[2521]: exiting
Apr 6 07:58:03 mail named[2560]: starting BIND 9.3.4-P1.1 -u bind
Apr 6 07:58:03 mail named[2560]: found 1 CPU, using 1 worker thread
Apr 6 07:58:03 mail named[2560]: loading configuration from '/etc/bind/named.conf'
Apr 6 07:58:03 mail named[2560]: listening on IPv6 interfaces, port 53
Apr 6 07:58:03 mail named[2560]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 6 07:58:03 mail named[2560]: listening on IPv4 interface eth1, 10.0.0.250#53
Apr 6 07:58:03 mail named[2560]: listening on IPv4 interface eth0, xxx.xx.xx.118#53
Apr 6 07:58:03 mail named[2560]: command channel listening on 127.0.0.1#953
Apr 6 07:58:03 mail named[2560]: command channel listening on ::1#953
Apr 6 07:58:03 mail named[2560]: zone 0.in-addr.arpa/IN: loaded serial 1
Apr 6 07:58:03 mail named[2560]: zone 127.in-addr.arpa/IN: loaded serial 1
Apr 6 07:58:03 mail named[2560]: /etc/bind/db.118.xx.xx.xxx:10: 113/29.xx.xx.xxx.in-addr.arpa: bad owner name (check-names)
Apr 6 07:58:03 mail named[2560]: zone 113/29.xx.xx.xxx.in-addr.arpa/IN: loading master file /etc/bind/db.118.xx.xx.xxx: bad owner name (check-names)
Apr 6 07:58:03 mail named[2560]: zone 255.in-addr.arpa/IN: loaded serial 1
Apr 6 07:58:03 mail named[2560]: zone mydomain.com/IN: loaded serial 1
Apr 6 07:58:03 mail named[2560]: zone localhost/IN: loaded serial 1
Apr 6 07:58:03 mail named[2560]: running
Apr 6 08:12:46 mail -- MARK --
Apr 6 08:17:01 mail /USR/SBIN/CRON[2717]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 6 08:32:47 mail -- MARK --
Apr 6 08:52:47 mail -- MARK --
Apr 6 09:12:47 mail -- MARK --
Apr 6 09:17:01 mail /USR/SBIN/CRON[2722]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 6 09:32:47 mail -- MARK --
Apr 6 09:52:47 mail -- MARK --
Apr 6 10:12:48 mail -- MARK --
Apr 6 10:17:01 mail /USR/SBIN/CRON[2730]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 6 10:32:48 mail -- MARK --
Apr 6 10:36:56 mail named[2560]: lame server resolving 'www.gastronomiabrasil.com' (in 'gastronomiabrasil.com'?): 200.176.128.153#53
Apr 6 10:36:57 mail named[2560]: lame server resolving 'www.gastronomiabrasil.com' (in 'gastronomiabrasil.com'?): 200.177.96.11#53
Apr 6 10:52:48 mail -- MARK --
Apr 6 11:12:48 mail -- MARK --
Apr 6 11:17:01 mail /USR/SBIN/CRON[2751]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 6 11:20:04 mail named[2560]: shutting down: flushing changes
Apr 6 11:20:04 mail named[2560]: stopping command channel on 127.0.0.1#953
Apr 6 11:20:04 mail named[2560]: stopping command channel on ::1#953
Apr 6 11:20:04 mail named[2560]: no longer listening on ::#53
Apr 6 11:20:04 mail named[2560]: no longer listening on 127.0.0.1#53
Apr 6 11:20:04 mail named[2560]: no longer listening on 10.0.0.250#53
Apr 6 11:20:04 mail named[2560]: no longer listening on xxx.xx.xx.118#53
Apr 6 11:20:04 mail named[2560]: exiting
Apr 6 11:20:06 mail named[2777]: starting BIND 9.3.4-P1.1 -u bind
Apr 6 11:20:06 mail named[2777]: found 1 CPU, using 1 worker thread
Apr 6 11:20:06 mail named[2777]: loading configuration from '/etc/bind/named.conf'
Apr 6 11:20:06 mail named[2777]: listening on IPv6 interfaces, port 53
Apr 6 11:20:06 mail named[2777]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 6 11:20:06 mail named[2777]: listening on IPv4 interface eth1, 10.0.0.250#53
Apr 6 11:20:06 mail named[2777]: listening on IPv4 interface eth0, xxx.xx.xx.118#53
Apr 6 11:20:06 mail named[2777]: command channel listening on 127.0.0.1#953
Apr 6 11:20:06 mail named[2777]: command channel listening on ::1#953
Apr 6 11:20:06 mail named[2777]: zone 0.in-addr.arpa/IN: loaded serial 1
Apr 6 11:20:06 mail named[2777]: zone 127.in-addr.arpa/IN: loaded serial 1
Apr 6 11:20:06 mail named[2777]: /etc/bind/db.118.xx.xx.xxx:10: 113/29.xx.xx.xxx.in-addr.arpa: bad owner name (check-names)
Apr 6 11:20:06 mail named[2777]: zone 113/29.xx.xx.xxx.in-addr.arpa/IN: loading master file /etc/bind/db.118.xx.xx.xxx: bad owner name (check-names)
Apr 6 11:20:06 mail named[2777]: zone 255.in-addr.arpa/IN: loaded serial 1
Apr 6 11:20:06 mail named[2777]: zone mydomain.com/IN: loaded serial 10
Apr 6 11:20:06 mail named[2777]: zone localhost/IN: loaded serial 1
Apr 6 11:20:06 mail named[2777]: running
Apr 6 11:32:49 mail -- MARK --
Apr 6 11:52:49 mail -- MARK --

bathory · 04-06-2009, 01:26 PM

Edit /etc/named.conf and add a "check-names ignore;" in the 113/29.xx.xx.xxx.in-addr.arpa. definition, i.e. it should look like this:

Code:

...
zone "113/29.xx.xx.xx.in-addr.arpa"{
notify no;
type master;
check-names ignore;
file "/etc/bind/db.xx.xx.xx.xx";
};
...

jcvalim · 04-06-2009, 01:55 PM

Quote:

Originally Posted by bathory

Edit /etc/named.conf and add a "check-names ignore;" in the 113/29.xx.xx.xxx.in-addr.arpa. definition, i.e. it should look like this:

Code:

...
zone "113/29.xx.xx.xx.in-addr.arpa"{
notify no;
type master;
check-names ignore;
file "/etc/bind/db.xx.xx.xx.xx";
};
...

same changing the file as you requested, still not resolving name:

Check syslog:

Apr 6 15:40:28 mail named[2215]: command channel listening on ::1#953
Apr 6 15:40:28 mail named[2215]: zone 0.in-addr.arpa/IN: loaded serial 1
Apr 6 15:40:28 mail named[2215]: zone 127.in-addr.arpa/IN: loaded serial 1
Apr 6 15:40:28 mail named[2215]: dns_rdata_fromtext: /etc/bind/db.118.xx.xx.xxx:10: near 'mail.mydomain.com.': not a valid number
Apr 6 15:40:28 mail named[2215]: zone 113/29.xx.xx.xxx.in-addr.arpa/IN: loading master file /etc/bind/db.118.xx.xx.xxx: not a valid number
Apr 6 15:40:28 mail named[2215]: zone 255.in-addr.arpa/IN: loaded serial 1
Apr 6 15:40:28 mail named[2215]: zone mydomain.com/IN: loaded serial 10
Apr 6 15:40:28 mail named[2215]: zone localhost/IN: loaded serial 1
Apr 6 15:40:28 mail named[2215]: running
Apr 6 15:40:28 mail kernel: ACPI: Power Button (FF) [PWRF]
Apr 6 15:40:28 mail kernel: ACPI: Power Button (CM) [PWRB]
Apr 6 15:40:29 mail rpc.statd[2390]: Version 1.0.10 Starting
Apr 6 15:40:29 mail /usr/sbin/cron[2406]: (CRON) INFO (pidfile fd = 3)
Apr 6 15:40:29 mail /usr/sbin/cron[2407]: (CRON) STARTUP (fork ok)
Apr 6 15:40:29 mail /usr/sbin/cron[2407]: (CRON) INFO (Running @reboot jobs)
Apr 6 15:40:38 mail kernel: eth0: no IPv6 routers present
Apr 6 15:40:39 mail kernel: eth1: no IPv6 routers present