bind: fix conf.patch to remove configuration that causes failure
cover bind: fix conf.patch to remove configuration that causes failure
The following changes since commit 68ddb28a68ceb59cd1ed322c16143827ce1ac712:
distrodata_class: checkpkg make usage of latest_versionstring methods in bitbake fetcher (2014-11-28 13:59:52 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/bind-configuration
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=ChenQi/bind-configuration
Chen Qi (1):
bind: fix conf.patch to remove configuration that causes failure
meta/recipes-connectivity/bind/bind/conf.patch | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-)
Signature · 1 line
1.9.1
PATCH 1/1 bind: fix conf.patch to remove configuration that causes failure
conf.patch added db.255 confgiuration entry to named.conf. However, We don't have db.255 configuration file, so remove this entry to avoid the following failure.
zone 255.in-addr.arpa/IN: loading from master file /etc/bind/db.255 failed: file not found
--- meta/recipes-connectivity/bind/bind/conf.patch | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-)
meta/recipes-connectivity/bind/bind/conf.patch +1 -6
@@ -124,7 +124,7 @@ diff -urN bind-9.3.1.orig/conf/db.root bind-9.3.1/conf/db.root diff -urN bind-9.3.1.orig/conf/named.conf bind-9.3.1/conf/named.conf --- bind-9.3.1.orig/conf/named.conf 1970-01-01 01:00:00.000000000 +0100 +++ bind-9.3.1/conf/named.conf 2005-07-10 22:33:46.000000000 +0200 -@@ -0,0 +1,49 @@ +@@ -0,0 +1,44 @@ +// This is the primary configuration file for the BIND DNS server named. +// +// If you are just adding zones, please do that in /etc/bind/named.conf.local
@@ -155,11 +155,6 @@ diff -urN bind-9.3.1.orig/conf/named.conf bind-9.3.1/conf/named.conf + file "/etc/bind/db.0"; +}; + -+zone "255.in-addr.arpa" { -+ type master; -+ file "/etc/bind/db.255"; -+}; -+ +// zone "com" { type delegation-only; }; +// zone "net" { type delegation-only; }; +
Signature · 1 line
1.9.1
Quoted 4 lines · Chen Qi
conf.patch added db.255 confgiuration entry to named.conf. However, We don't have db.255 configuration file, so remove this entry to avoid the following failure.
Can you explain why the correct fix is to remove the reference to db.255, and not add a db.255 configuration file?
Ross
Quoted 11 lines · Ross
On 2 December 2014 at 06:00, Chen Qi <[email protected] <mailto:[email protected]>> wrote:
conf.patch added db.255 confgiuration entry to named.conf. However, We don't have db.255 configuration file, so remove this entry to avoid the following failure.
Can you explain why the correct fix is to remove the reference to db.255, and not add a db.255 configuration file?
Ross
Hi Ross,
Sorry for the late reply. I just noticed this email.
I chose to remove reference to db.255 because I saw there was no db.255. I didn't take a second thinking about this problem.
I will send out V2 by adding db.255 configuration file.
Best Regards,
Chen Qi