named checkhints spots the following: named-sdb[21428]: checkhints: L.ROOT-SERVERS.NET/A (199.7.83.42) missing from hi nts named-sdb[21428]: checkhints: L.ROOT-SERVERS.NET/A (198.32.64.12) extra record i n hints The easiest solution is to download named.root from internic. Please note, that the included root is from 2004 and the actual version is from 2008. See diff: [root@malz named]# diff root named.root 12,14c12,13 < ; last update: Jan 29, 2004 < ; related version of root zone: 2004012900 < ; --- > ; last update: Feb 04, 2008 > ; related version of root zone: 2008020400 19a19 > A.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:BA3E::2:30 44a45 > F.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:2f::f 54a56 > H.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:1::803f:235 64a67 > J.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:C27::2:30 69a73 > K.ROOT-SERVERS.NET. 3600000 AAAA 2001:7fd::1 74c78 < L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12 --- > L.ROOT-SERVERS.NET. 3600000 A 199.7.83.42 79a84 > M.ROOT-SERVERS.NET. 3600000 AAAA 2001:dc3::35 I could also imagine a cronjob that updates the root file on a regular basis (eg. once a month). What do you thing?
(In reply to comment #0) File /var/named/named.ca is used as "root hints" file, not /var/named/named.root. named.ca is up2date. > > I could also imagine a cronjob that updates the root file on a regular basis > (eg. once a month). What do you thing? It is not needed because root zone is not changed so often.
Oh. Then this is a very old config from myself (migrated from release to release...) - sorry for bugging! :-(