B.I.N.D. issues.

Issues related to configuring your network
User avatar
avij
Retired Moderator
Posts: 3046
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: B.I.N.D. issues.

Post by avij » 2014/04/14 21:46:45

You have extra semicolons on these lines:

Code: Select all

zone "." IN {;
...
zone "strangefruitradio.net" IN {; # FORWARD Zone file and configuration - put in your DOMAINNAME
You didn't have them in your initial configuration that you posted. Get rid of those semicolons that you added and try restarting named again.

CharmingNathan
Posts: 155
Joined: 2014/04/09 12:48:55

Re: B.I.N.D. issues.

Post by CharmingNathan » 2014/04/14 21:56:27

avij wrote:You have extra semicolons on these lines:

Code: Select all

zone "." IN {;
...
zone "strangefruitradio.net" IN {; # FORWARD Zone file and configuration - put in your DOMAINNAME
You didn't have them in your initial configuration that you posted. Get rid of those semicolons that you added and try restarting named again.
I believe I have got the above corrected:

zone "." IN {
type hint;
file "named.ca";
};

zone "strangefruitradio.net" IN { # FORWARD Zone file and configuration - put in your DOMAINNAME
type master;
file "fwd.strangefruitradio.net";
allow-update { none; };

When I run:

Starting named:
Error in named configuration:
/etc/named.conf:32: '}' expected near ';'

User avatar
avij
Retired Moderator
Posts: 3046
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: B.I.N.D. issues.

Post by avij » 2014/04/14 21:59:44

Perhaps there's an extra semicolon near line 32?

drk
Posts: 405
Joined: 2014/01/30 20:38:28

Re: B.I.N.D. issues.

Post by drk » 2014/04/14 22:06:14

CharmingNathan wrote: #zone "1.168.192.in-addr.arpa" IN { # REVERSE Zone file and configuration
# type master;
# file "rev.strangefruitradio.net";
# allow-update { none; };
#;};
I don't think "#"s are welcome in named.conf. Try changing them to "//" or delete the lines altogether.

* Edit: The "#"s are allowed per the man page.

User avatar
TrevorH
Site Admin
Posts: 33218
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: B.I.N.D. issues.

Post by TrevorH » 2014/04/14 22:14:32

It would probably also help in diagnosis if you would post the entire file, preferably wrapped in [code][/code] tags to preserve formatting. You can see what line 32 is, we cannot.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

CharmingNathan
Posts: 155
Joined: 2014/04/09 12:48:55

Re: B.I.N.D. issues.

Post by CharmingNathan » 2014/04/14 22:15:28

avij wrote:Perhaps there's an extra semicolon near line 32?
I am using Nano to view this file, but it doesn't number the individual lines, would you recommend another texxt editor?

CharmingNathan
Posts: 155
Joined: 2014/04/09 12:48:55

Re: B.I.N.D. issues.

Post by CharmingNathan » 2014/04/14 22:21:07

avij wrote:Perhaps there's an extra semicolon near line 32?
Okay, got that last semi-colon - THANK YOU avij!

[root@nathan-desktop ~]# nano /etc/named.conf
[root@nathan-desktop ~]# service named start
Starting named: [ OK ]
[root@nathan-desktop ~]#

Now, all I have to do is get Apache working and test it!!!

User avatar
avij
Retired Moderator
Posts: 3046
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: B.I.N.D. issues.

Post by avij » 2014/04/14 22:22:47

If you press CTRL-C within nano, it will show you the current line number where the cursor is positioned, like " [ line 16/34 (47%), col 1/3 (33%), char 193/666 (28%) ]".

Do note that the actual error may also be a few lines before or after the reported line number. Navigate to the reported line number and look around a bit for any possible errors.

[edit: oh, you got it working, excellent]

Post Reply