This is a discussion on strange rndc behavior within the Bind Users forums, part of the DNS and Related Forums category; Hi, friends. Bind 9.2.2 Running 'rndc status' got time out. Configure file is ok, the weird thing is ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hi, friends.
Bind 9.2.2 Running 'rndc status' got time out. Configure file is ok, the weird thing is the netstat -an output: bash-2.03# netstat -an|grep 953 127.0.0.1.953 *.* 0 0 24576 0 LISTEN 10.2.172.36.37433 127.0.0.1.953 0 0 24820 0 SYN_SENT look out , the connection comes from 10.2.172.36, the ip address of my hme0 interface, not 127.0.0.1 ! When I'm looking at a working server, the rndc socket come from 127.0.0.1. So, I think this is the culprit, if you remember, the default configurations of named.conf is only accept connections from 127.0.0.1. But I have no idea why rndc connect named through ip address of the interface , while not 127.0.0.1. anybody have hints/suggestion/advice? likun |