syntax error /etc/named.conf [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I am very new to DNS configurations. I am trying to configure DNS on RHEL 5 for study purposes.



I have set up forward zones, reverse zones, and named.conf files in order to get the DNS working, but when I run service named start, I get the following error:enter image description here



OS: RHEL 5



IPs I am using 172.168.190.1 ... 172.168.190.50



My /etc/named.conf file is as follows:



options 
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
listen-on port 53 any; ;
;

zone "oracleexpert.com" IN
type master;
file "oracleexpert.com.fwd.zone";
allow-update none; ;
;

zone "localhost" IN
type master;
file "localhost.fwd.zone";
allow-update none; ;
;

zone "190.168.172.in-addr.arpa." IN
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;

zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa." IN
type master;
file "named.ip6.local";
allow-update none; ;
;

zone "255.in-addr.arpa." IN
type master;
file "named.broadcast";
allow-update none; ;
;

zone "0.in-addr.arpa." IN
type master;
file "named.zero";
allow-update none; ;
;

include "/etc/rndc.key";

50,19 Bot


Please help. Thanking you.



Here is the output of sed -n l /etc/named.conf:



options $
tdirectory "/var/named";$
tlisten-on port 53 any; ;$
;$
$
zone "oracleexpert.com" IN $
ttype master;$
tfile "oracleexpert.com.fwd.zone";$
tallow-update none; ;$
;$
$
zone "localhost" IN $
ttype master;$
tfile "localhost.fwd.zone";$
tallow-update none; ;$
;$
$
zone "190.168.172.in-addr.arpa" IN $
ttype master;$
tfile "172.168.190.rev.zone";$
tallow-update none; ;$
;$
$
zone "0.0.127.in-addr-arpa" IN $
ttype master;$
tfile "localhost.rev.zone";$
tallow-update none; ;$
;$
$
zone "255.in-addr.arpa" IN $
ttype master;$
tfile "named.broadcast";$
tallow-update none; ;$
;$
$
zone "0.in-addr.arpa" IN $
ttype master;$
tfile "named.zero";$
tallow-update none; ;$
;$
$
include "/etc/rndc.key";$
[root@alpha ~]#






share|improve this question














closed as off-topic by terdon♦ Oct 23 '17 at 7:35


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – terdon
If this question can be reworded to fit the rules in the help center, please edit the question.








  • 1




    Not to mention that RHEL5 is EOF (End of Life) and isn't supported anymore.
    – Valentin B
    Oct 21 '17 at 10:28






  • 4




    Don't post images of text, please.
    – Tomasz
    Oct 21 '17 at 10:28










  • Apologies. I will keep that in mind.
    – Avinash Pawar
    Oct 21 '17 at 10:45










  • You are showing two different files in the question. Which file do you have issues with?
    – Kusalananda
    Oct 21 '17 at 15:52






  • 1




    The point is that you have posted two different versions of /etc/named.conf. You should edit your question to show the same version of the file in both cat and sed -n l forms, and the error message that goes with that version (because the line numbers have changed). In general, your question should say what you have done to try to solve the problem. Specifically, you should say something like, “I had dots at the ends of names, e.g., arpa., and I took them out (→ arpa), and I had a dump-file and a statistics-file, and I took them out, and yet I get the same error.”
    – G-Man
    Oct 21 '17 at 19:56















up vote
0
down vote

favorite












I am very new to DNS configurations. I am trying to configure DNS on RHEL 5 for study purposes.



I have set up forward zones, reverse zones, and named.conf files in order to get the DNS working, but when I run service named start, I get the following error:enter image description here



OS: RHEL 5



IPs I am using 172.168.190.1 ... 172.168.190.50



My /etc/named.conf file is as follows:



options 
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
listen-on port 53 any; ;
;

zone "oracleexpert.com" IN
type master;
file "oracleexpert.com.fwd.zone";
allow-update none; ;
;

zone "localhost" IN
type master;
file "localhost.fwd.zone";
allow-update none; ;
;

zone "190.168.172.in-addr.arpa." IN
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;

zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa." IN
type master;
file "named.ip6.local";
allow-update none; ;
;

zone "255.in-addr.arpa." IN
type master;
file "named.broadcast";
allow-update none; ;
;

zone "0.in-addr.arpa." IN
type master;
file "named.zero";
allow-update none; ;
;

include "/etc/rndc.key";

50,19 Bot


Please help. Thanking you.



Here is the output of sed -n l /etc/named.conf:



options $
tdirectory "/var/named";$
tlisten-on port 53 any; ;$
;$
$
zone "oracleexpert.com" IN $
ttype master;$
tfile "oracleexpert.com.fwd.zone";$
tallow-update none; ;$
;$
$
zone "localhost" IN $
ttype master;$
tfile "localhost.fwd.zone";$
tallow-update none; ;$
;$
$
zone "190.168.172.in-addr.arpa" IN $
ttype master;$
tfile "172.168.190.rev.zone";$
tallow-update none; ;$
;$
$
zone "0.0.127.in-addr-arpa" IN $
ttype master;$
tfile "localhost.rev.zone";$
tallow-update none; ;$
;$
$
zone "255.in-addr.arpa" IN $
ttype master;$
tfile "named.broadcast";$
tallow-update none; ;$
;$
$
zone "0.in-addr.arpa" IN $
ttype master;$
tfile "named.zero";$
tallow-update none; ;$
;$
$
include "/etc/rndc.key";$
[root@alpha ~]#






share|improve this question














closed as off-topic by terdon♦ Oct 23 '17 at 7:35


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – terdon
If this question can be reworded to fit the rules in the help center, please edit the question.








  • 1




    Not to mention that RHEL5 is EOF (End of Life) and isn't supported anymore.
    – Valentin B
    Oct 21 '17 at 10:28






  • 4




    Don't post images of text, please.
    – Tomasz
    Oct 21 '17 at 10:28










  • Apologies. I will keep that in mind.
    – Avinash Pawar
    Oct 21 '17 at 10:45










  • You are showing two different files in the question. Which file do you have issues with?
    – Kusalananda
    Oct 21 '17 at 15:52






  • 1




    The point is that you have posted two different versions of /etc/named.conf. You should edit your question to show the same version of the file in both cat and sed -n l forms, and the error message that goes with that version (because the line numbers have changed). In general, your question should say what you have done to try to solve the problem. Specifically, you should say something like, “I had dots at the ends of names, e.g., arpa., and I took them out (→ arpa), and I had a dump-file and a statistics-file, and I took them out, and yet I get the same error.”
    – G-Man
    Oct 21 '17 at 19:56













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am very new to DNS configurations. I am trying to configure DNS on RHEL 5 for study purposes.



I have set up forward zones, reverse zones, and named.conf files in order to get the DNS working, but when I run service named start, I get the following error:enter image description here



OS: RHEL 5



IPs I am using 172.168.190.1 ... 172.168.190.50



My /etc/named.conf file is as follows:



options 
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
listen-on port 53 any; ;
;

zone "oracleexpert.com" IN
type master;
file "oracleexpert.com.fwd.zone";
allow-update none; ;
;

zone "localhost" IN
type master;
file "localhost.fwd.zone";
allow-update none; ;
;

zone "190.168.172.in-addr.arpa." IN
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;

zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa." IN
type master;
file "named.ip6.local";
allow-update none; ;
;

zone "255.in-addr.arpa." IN
type master;
file "named.broadcast";
allow-update none; ;
;

zone "0.in-addr.arpa." IN
type master;
file "named.zero";
allow-update none; ;
;

include "/etc/rndc.key";

50,19 Bot


Please help. Thanking you.



Here is the output of sed -n l /etc/named.conf:



options $
tdirectory "/var/named";$
tlisten-on port 53 any; ;$
;$
$
zone "oracleexpert.com" IN $
ttype master;$
tfile "oracleexpert.com.fwd.zone";$
tallow-update none; ;$
;$
$
zone "localhost" IN $
ttype master;$
tfile "localhost.fwd.zone";$
tallow-update none; ;$
;$
$
zone "190.168.172.in-addr.arpa" IN $
ttype master;$
tfile "172.168.190.rev.zone";$
tallow-update none; ;$
;$
$
zone "0.0.127.in-addr-arpa" IN $
ttype master;$
tfile "localhost.rev.zone";$
tallow-update none; ;$
;$
$
zone "255.in-addr.arpa" IN $
ttype master;$
tfile "named.broadcast";$
tallow-update none; ;$
;$
$
zone "0.in-addr.arpa" IN $
ttype master;$
tfile "named.zero";$
tallow-update none; ;$
;$
$
include "/etc/rndc.key";$
[root@alpha ~]#






share|improve this question














I am very new to DNS configurations. I am trying to configure DNS on RHEL 5 for study purposes.



I have set up forward zones, reverse zones, and named.conf files in order to get the DNS working, but when I run service named start, I get the following error:enter image description here



OS: RHEL 5



IPs I am using 172.168.190.1 ... 172.168.190.50



My /etc/named.conf file is as follows:



options 
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
listen-on port 53 any; ;
;

zone "oracleexpert.com" IN
type master;
file "oracleexpert.com.fwd.zone";
allow-update none; ;
;

zone "localhost" IN
type master;
file "localhost.fwd.zone";
allow-update none; ;
;

zone "190.168.172.in-addr.arpa." IN
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;

zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa." IN
type master;
file "named.ip6.local";
allow-update none; ;
;

zone "255.in-addr.arpa." IN
type master;
file "named.broadcast";
allow-update none; ;
;

zone "0.in-addr.arpa." IN
type master;
file "named.zero";
allow-update none; ;
;

include "/etc/rndc.key";

50,19 Bot


Please help. Thanking you.



Here is the output of sed -n l /etc/named.conf:



options $
tdirectory "/var/named";$
tlisten-on port 53 any; ;$
;$
$
zone "oracleexpert.com" IN $
ttype master;$
tfile "oracleexpert.com.fwd.zone";$
tallow-update none; ;$
;$
$
zone "localhost" IN $
ttype master;$
tfile "localhost.fwd.zone";$
tallow-update none; ;$
;$
$
zone "190.168.172.in-addr.arpa" IN $
ttype master;$
tfile "172.168.190.rev.zone";$
tallow-update none; ;$
;$
$
zone "0.0.127.in-addr-arpa" IN $
ttype master;$
tfile "localhost.rev.zone";$
tallow-update none; ;$
;$
$
zone "255.in-addr.arpa" IN $
ttype master;$
tfile "named.broadcast";$
tallow-update none; ;$
;$
$
zone "0.in-addr.arpa" IN $
ttype master;$
tfile "named.zero";$
tallow-update none; ;$
;$
$
include "/etc/rndc.key";$
[root@alpha ~]#








share|improve this question













share|improve this question




share|improve this question








edited Feb 22 at 13:24









Rui F Ribeiro

36.1k1271114




36.1k1271114










asked Oct 21 '17 at 10:17









Avinash Pawar

83




83




closed as off-topic by terdon♦ Oct 23 '17 at 7:35


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – terdon
If this question can be reworded to fit the rules in the help center, please edit the question.




closed as off-topic by terdon♦ Oct 23 '17 at 7:35


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – terdon
If this question can be reworded to fit the rules in the help center, please edit the question.







  • 1




    Not to mention that RHEL5 is EOF (End of Life) and isn't supported anymore.
    – Valentin B
    Oct 21 '17 at 10:28






  • 4




    Don't post images of text, please.
    – Tomasz
    Oct 21 '17 at 10:28










  • Apologies. I will keep that in mind.
    – Avinash Pawar
    Oct 21 '17 at 10:45










  • You are showing two different files in the question. Which file do you have issues with?
    – Kusalananda
    Oct 21 '17 at 15:52






  • 1




    The point is that you have posted two different versions of /etc/named.conf. You should edit your question to show the same version of the file in both cat and sed -n l forms, and the error message that goes with that version (because the line numbers have changed). In general, your question should say what you have done to try to solve the problem. Specifically, you should say something like, “I had dots at the ends of names, e.g., arpa., and I took them out (→ arpa), and I had a dump-file and a statistics-file, and I took them out, and yet I get the same error.”
    – G-Man
    Oct 21 '17 at 19:56













  • 1




    Not to mention that RHEL5 is EOF (End of Life) and isn't supported anymore.
    – Valentin B
    Oct 21 '17 at 10:28






  • 4




    Don't post images of text, please.
    – Tomasz
    Oct 21 '17 at 10:28










  • Apologies. I will keep that in mind.
    – Avinash Pawar
    Oct 21 '17 at 10:45










  • You are showing two different files in the question. Which file do you have issues with?
    – Kusalananda
    Oct 21 '17 at 15:52






  • 1




    The point is that you have posted two different versions of /etc/named.conf. You should edit your question to show the same version of the file in both cat and sed -n l forms, and the error message that goes with that version (because the line numbers have changed). In general, your question should say what you have done to try to solve the problem. Specifically, you should say something like, “I had dots at the ends of names, e.g., arpa., and I took them out (→ arpa), and I had a dump-file and a statistics-file, and I took them out, and yet I get the same error.”
    – G-Man
    Oct 21 '17 at 19:56








1




1




Not to mention that RHEL5 is EOF (End of Life) and isn't supported anymore.
– Valentin B
Oct 21 '17 at 10:28




Not to mention that RHEL5 is EOF (End of Life) and isn't supported anymore.
– Valentin B
Oct 21 '17 at 10:28




4




4




Don't post images of text, please.
– Tomasz
Oct 21 '17 at 10:28




Don't post images of text, please.
– Tomasz
Oct 21 '17 at 10:28












Apologies. I will keep that in mind.
– Avinash Pawar
Oct 21 '17 at 10:45




Apologies. I will keep that in mind.
– Avinash Pawar
Oct 21 '17 at 10:45












You are showing two different files in the question. Which file do you have issues with?
– Kusalananda
Oct 21 '17 at 15:52




You are showing two different files in the question. Which file do you have issues with?
– Kusalananda
Oct 21 '17 at 15:52




1




1




The point is that you have posted two different versions of /etc/named.conf. You should edit your question to show the same version of the file in both cat and sed -n l forms, and the error message that goes with that version (because the line numbers have changed). In general, your question should say what you have done to try to solve the problem. Specifically, you should say something like, “I had dots at the ends of names, e.g., arpa., and I took them out (→ arpa), and I had a dump-file and a statistics-file, and I took them out, and yet I get the same error.”
– G-Man
Oct 21 '17 at 19:56





The point is that you have posted two different versions of /etc/named.conf. You should edit your question to show the same version of the file in both cat and sed -n l forms, and the error message that goes with that version (because the line numbers have changed). In general, your question should say what you have done to try to solve the problem. Specifically, you should say something like, “I had dots at the ends of names, e.g., arpa., and I took them out (→ arpa), and I had a dump-file and a statistics-file, and I took them out, and yet I get the same error.”
– G-Man
Oct 21 '17 at 19:56











2 Answers
2






active

oldest

votes

















up vote
1
down vote



accepted










Take out the dots. Instead of:



zone "190.168.172.in-addr.arpa." IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;


It should be:



zone "190.168.172.in-addr.arpa" IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa" IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;





share|improve this answer




















  • Thanks for reply, I did take out the dots, yet the same error :-(
    – Avinash Pawar
    Oct 21 '17 at 10:43










  • @AvinashPawar Can you run sed -n l /etc/named.conf and show us how it looks like?
    – Valentin B
    Oct 21 '17 at 10:45











  • Sorry, the comments box is reluctant to accept all the characters. The o/p for sed -n l /etc/named.conf is almost 1000 char long
    – Avinash Pawar
    Oct 21 '17 at 10:50






  • 3




    You can update your question, no need to paste it as comment.
    – Valentin B
    Oct 21 '17 at 11:12






  • 1




    Don’t say “no need to paste it as comment”; say “Don’t paste it as comment!”  Information that clarifies or refines the question should always be added to the question, even if it’s only the answer to a “Yes” or “No” question, or some other very short phrase. (Of course it should be comprehensible in context, so don’t say just “Yes”; say (for example) “I have rebooted since the last time I edited the file and the problem persists.”) It is good practice to then post a comment saying that you have updated the question, @-pinging the person who asked for the clarification.
    – G-Man
    Oct 21 '17 at 19:41

















up vote
0
down vote













Well, thank you very much for all your support. I got it rectified. It was a silly mistake I was doing. I had /etc/named.conf and /var/named/chroot/etc/named.conf files and both were slightly different from one another. I just had to match them both in order to get it working.






share|improve this answer




















  • To avoid problems do an hard link (not a symlink) between the two (hoping there are on the same filesystem otherwise you can't). Or just remove /etc/named.conf
    – Patrick Mevzek
    Oct 22 '17 at 22:55










  • Yes, they are on the same filesystem and I created an hard link. Thanks.
    – Avinash Pawar
    Oct 23 '17 at 5:23

















2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










Take out the dots. Instead of:



zone "190.168.172.in-addr.arpa." IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;


It should be:



zone "190.168.172.in-addr.arpa" IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa" IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;





share|improve this answer




















  • Thanks for reply, I did take out the dots, yet the same error :-(
    – Avinash Pawar
    Oct 21 '17 at 10:43










  • @AvinashPawar Can you run sed -n l /etc/named.conf and show us how it looks like?
    – Valentin B
    Oct 21 '17 at 10:45











  • Sorry, the comments box is reluctant to accept all the characters. The o/p for sed -n l /etc/named.conf is almost 1000 char long
    – Avinash Pawar
    Oct 21 '17 at 10:50






  • 3




    You can update your question, no need to paste it as comment.
    – Valentin B
    Oct 21 '17 at 11:12






  • 1




    Don’t say “no need to paste it as comment”; say “Don’t paste it as comment!”  Information that clarifies or refines the question should always be added to the question, even if it’s only the answer to a “Yes” or “No” question, or some other very short phrase. (Of course it should be comprehensible in context, so don’t say just “Yes”; say (for example) “I have rebooted since the last time I edited the file and the problem persists.”) It is good practice to then post a comment saying that you have updated the question, @-pinging the person who asked for the clarification.
    – G-Man
    Oct 21 '17 at 19:41














up vote
1
down vote



accepted










Take out the dots. Instead of:



zone "190.168.172.in-addr.arpa." IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;


It should be:



zone "190.168.172.in-addr.arpa" IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa" IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;





share|improve this answer




















  • Thanks for reply, I did take out the dots, yet the same error :-(
    – Avinash Pawar
    Oct 21 '17 at 10:43










  • @AvinashPawar Can you run sed -n l /etc/named.conf and show us how it looks like?
    – Valentin B
    Oct 21 '17 at 10:45











  • Sorry, the comments box is reluctant to accept all the characters. The o/p for sed -n l /etc/named.conf is almost 1000 char long
    – Avinash Pawar
    Oct 21 '17 at 10:50






  • 3




    You can update your question, no need to paste it as comment.
    – Valentin B
    Oct 21 '17 at 11:12






  • 1




    Don’t say “no need to paste it as comment”; say “Don’t paste it as comment!”  Information that clarifies or refines the question should always be added to the question, even if it’s only the answer to a “Yes” or “No” question, or some other very short phrase. (Of course it should be comprehensible in context, so don’t say just “Yes”; say (for example) “I have rebooted since the last time I edited the file and the problem persists.”) It is good practice to then post a comment saying that you have updated the question, @-pinging the person who asked for the clarification.
    – G-Man
    Oct 21 '17 at 19:41












up vote
1
down vote



accepted







up vote
1
down vote



accepted






Take out the dots. Instead of:



zone "190.168.172.in-addr.arpa." IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;


It should be:



zone "190.168.172.in-addr.arpa" IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa" IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;





share|improve this answer












Take out the dots. Instead of:



zone "190.168.172.in-addr.arpa." IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa." IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;


It should be:



zone "190.168.172.in-addr.arpa" IN 
type master;
file "172.168.190.rev.zone";
allow-update none; ;
;

zone "0.0.127.in-addr.arpa" IN
type master;
file "localhost.rev.zone";
allow-update none; ;
;






share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 21 '17 at 10:29









Rui F Ribeiro

36.1k1271114




36.1k1271114











  • Thanks for reply, I did take out the dots, yet the same error :-(
    – Avinash Pawar
    Oct 21 '17 at 10:43










  • @AvinashPawar Can you run sed -n l /etc/named.conf and show us how it looks like?
    – Valentin B
    Oct 21 '17 at 10:45











  • Sorry, the comments box is reluctant to accept all the characters. The o/p for sed -n l /etc/named.conf is almost 1000 char long
    – Avinash Pawar
    Oct 21 '17 at 10:50






  • 3




    You can update your question, no need to paste it as comment.
    – Valentin B
    Oct 21 '17 at 11:12






  • 1




    Don’t say “no need to paste it as comment”; say “Don’t paste it as comment!”  Information that clarifies or refines the question should always be added to the question, even if it’s only the answer to a “Yes” or “No” question, or some other very short phrase. (Of course it should be comprehensible in context, so don’t say just “Yes”; say (for example) “I have rebooted since the last time I edited the file and the problem persists.”) It is good practice to then post a comment saying that you have updated the question, @-pinging the person who asked for the clarification.
    – G-Man
    Oct 21 '17 at 19:41
















  • Thanks for reply, I did take out the dots, yet the same error :-(
    – Avinash Pawar
    Oct 21 '17 at 10:43










  • @AvinashPawar Can you run sed -n l /etc/named.conf and show us how it looks like?
    – Valentin B
    Oct 21 '17 at 10:45











  • Sorry, the comments box is reluctant to accept all the characters. The o/p for sed -n l /etc/named.conf is almost 1000 char long
    – Avinash Pawar
    Oct 21 '17 at 10:50






  • 3




    You can update your question, no need to paste it as comment.
    – Valentin B
    Oct 21 '17 at 11:12






  • 1




    Don’t say “no need to paste it as comment”; say “Don’t paste it as comment!”  Information that clarifies or refines the question should always be added to the question, even if it’s only the answer to a “Yes” or “No” question, or some other very short phrase. (Of course it should be comprehensible in context, so don’t say just “Yes”; say (for example) “I have rebooted since the last time I edited the file and the problem persists.”) It is good practice to then post a comment saying that you have updated the question, @-pinging the person who asked for the clarification.
    – G-Man
    Oct 21 '17 at 19:41















Thanks for reply, I did take out the dots, yet the same error :-(
– Avinash Pawar
Oct 21 '17 at 10:43




Thanks for reply, I did take out the dots, yet the same error :-(
– Avinash Pawar
Oct 21 '17 at 10:43












@AvinashPawar Can you run sed -n l /etc/named.conf and show us how it looks like?
– Valentin B
Oct 21 '17 at 10:45





@AvinashPawar Can you run sed -n l /etc/named.conf and show us how it looks like?
– Valentin B
Oct 21 '17 at 10:45













Sorry, the comments box is reluctant to accept all the characters. The o/p for sed -n l /etc/named.conf is almost 1000 char long
– Avinash Pawar
Oct 21 '17 at 10:50




Sorry, the comments box is reluctant to accept all the characters. The o/p for sed -n l /etc/named.conf is almost 1000 char long
– Avinash Pawar
Oct 21 '17 at 10:50




3




3




You can update your question, no need to paste it as comment.
– Valentin B
Oct 21 '17 at 11:12




You can update your question, no need to paste it as comment.
– Valentin B
Oct 21 '17 at 11:12




1




1




Don’t say “no need to paste it as comment”; say “Don’t paste it as comment!”  Information that clarifies or refines the question should always be added to the question, even if it’s only the answer to a “Yes” or “No” question, or some other very short phrase. (Of course it should be comprehensible in context, so don’t say just “Yes”; say (for example) “I have rebooted since the last time I edited the file and the problem persists.”) It is good practice to then post a comment saying that you have updated the question, @-pinging the person who asked for the clarification.
– G-Man
Oct 21 '17 at 19:41




Don’t say “no need to paste it as comment”; say “Don’t paste it as comment!”  Information that clarifies or refines the question should always be added to the question, even if it’s only the answer to a “Yes” or “No” question, or some other very short phrase. (Of course it should be comprehensible in context, so don’t say just “Yes”; say (for example) “I have rebooted since the last time I edited the file and the problem persists.”) It is good practice to then post a comment saying that you have updated the question, @-pinging the person who asked for the clarification.
– G-Man
Oct 21 '17 at 19:41












up vote
0
down vote













Well, thank you very much for all your support. I got it rectified. It was a silly mistake I was doing. I had /etc/named.conf and /var/named/chroot/etc/named.conf files and both were slightly different from one another. I just had to match them both in order to get it working.






share|improve this answer




















  • To avoid problems do an hard link (not a symlink) between the two (hoping there are on the same filesystem otherwise you can't). Or just remove /etc/named.conf
    – Patrick Mevzek
    Oct 22 '17 at 22:55










  • Yes, they are on the same filesystem and I created an hard link. Thanks.
    – Avinash Pawar
    Oct 23 '17 at 5:23














up vote
0
down vote













Well, thank you very much for all your support. I got it rectified. It was a silly mistake I was doing. I had /etc/named.conf and /var/named/chroot/etc/named.conf files and both were slightly different from one another. I just had to match them both in order to get it working.






share|improve this answer




















  • To avoid problems do an hard link (not a symlink) between the two (hoping there are on the same filesystem otherwise you can't). Or just remove /etc/named.conf
    – Patrick Mevzek
    Oct 22 '17 at 22:55










  • Yes, they are on the same filesystem and I created an hard link. Thanks.
    – Avinash Pawar
    Oct 23 '17 at 5:23












up vote
0
down vote










up vote
0
down vote









Well, thank you very much for all your support. I got it rectified. It was a silly mistake I was doing. I had /etc/named.conf and /var/named/chroot/etc/named.conf files and both were slightly different from one another. I just had to match them both in order to get it working.






share|improve this answer












Well, thank you very much for all your support. I got it rectified. It was a silly mistake I was doing. I had /etc/named.conf and /var/named/chroot/etc/named.conf files and both were slightly different from one another. I just had to match them both in order to get it working.







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 22 '17 at 11:46









Avinash Pawar

83




83











  • To avoid problems do an hard link (not a symlink) between the two (hoping there are on the same filesystem otherwise you can't). Or just remove /etc/named.conf
    – Patrick Mevzek
    Oct 22 '17 at 22:55










  • Yes, they are on the same filesystem and I created an hard link. Thanks.
    – Avinash Pawar
    Oct 23 '17 at 5:23
















  • To avoid problems do an hard link (not a symlink) between the two (hoping there are on the same filesystem otherwise you can't). Or just remove /etc/named.conf
    – Patrick Mevzek
    Oct 22 '17 at 22:55










  • Yes, they are on the same filesystem and I created an hard link. Thanks.
    – Avinash Pawar
    Oct 23 '17 at 5:23















To avoid problems do an hard link (not a symlink) between the two (hoping there are on the same filesystem otherwise you can't). Or just remove /etc/named.conf
– Patrick Mevzek
Oct 22 '17 at 22:55




To avoid problems do an hard link (not a symlink) between the two (hoping there are on the same filesystem otherwise you can't). Or just remove /etc/named.conf
– Patrick Mevzek
Oct 22 '17 at 22:55












Yes, they are on the same filesystem and I created an hard link. Thanks.
– Avinash Pawar
Oct 23 '17 at 5:23




Yes, they are on the same filesystem and I created an hard link. Thanks.
– Avinash Pawar
Oct 23 '17 at 5:23


Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay