[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 183
  • Last Modified:

named problem

Recently, in my /var/log/messages, a few error lines about named show up:
bind(dfd=20,[127.0.0.1].53): permission denied
deleting interface [127.0.0.1].53
Same thing for my external IP address.
However, DNS server works fine (tried nslookup with my box as server). I can't think of anything that has changed. What do these lines mean and how do I get rid of them?
Thx
0
Tomdp
Asked:
Tomdp
1 Solution
 
ventolinCommented:
These permission problems usually involve a socket or the directory in which it resides. The general rule here is that the directory should have read and write permissions for its respective user, and the socket (or named pipe on some operating systems) should be owned by the respective user.
0
 
TomdpAuthor Commented:
Please be more specific. Besides, like I said, nothing changed and these messages only showed up some days ago
0
 
ColinMcKinnonCommented:
The obvious thing is that someone tried to start a second instance of named - which failed because it couldn't listen on ports which were already in use. Your first instance is still answering queries.
0
 
flatsCommented:
Do you have a local DNS entry set up?
In named.conf:

zone "localhost" { type master; notify no; file "localhost"; };

zone "0.0.127.in-addr.arpa" in { type master; notify no; file "127.0.0"; };


###### File: 127.0.0
$TTL 3600
@    in      soa     localhost. postmaster.localhost. (
                                1999110901      ;serial
                                3600            ;refresh
                                1800            ;retry
                                604800          ;expiration
                                3600 )          ;minimum

                        ns      localhost.

1                       ptr     localhost.
#############################

#####File: localhost
$TTL 3600
@  in      soa     localhost. postmaster.localhost. (
                                1999110901      ;serial
                                3600            ;refresh
                                1800            ;retry
                                604800          ;expiration
                                3600 )          ;minimum

                        NS      localhost.

                        A       127.0.0.1
#############################

Of course if you have DNS setup and it works, this was probably a very remedial answer.  What version of bind are you on?

0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now