This is a discussion on Re: rndc reload problems - DNS ; Kirk: Thanks for your reply! With your suggestions, I found the my machine only listen 953 port on 127.0.0.1, NOT on 192.168.1.18. So if I change the inet statement as "inet *", I can now reload successfully both with 127.0.0.1 ...
Kirk: Thanks for your reply!
With your suggestions, I found the my machine only listen 953 port on
127.0.0.1, NOT on 192.168.1.18. So if I change the inet statement as "inet
*", I can now reload successfully both with 127.0.0.1 and 192.168.1.18.
Thanks a lot for your help!
> Li Tongxi wrote:
> > Hi, All: I meet a strange problem with my rndc. I'm using BIND9.3.2 on
> > WindowsXP and my DNS's IP is 192.168.1.18. In the DNS server, if I use
> > "rndc -s 127.0.0.1 reload", I can see the reload works fine. But if I
> > "rndc -s 192.168.1.18 reload", it will report connection refused. With a
> > "-V" option, it reports following:
> > "
> > C:\named\bin>rndc -s 192.168.1.18 -V reload
> > create memory context
> > create socket manager
> > create task manager
> > create task
> > create logging context
> > setting log tag
> > creating log channel
> > enabling log channel
> > create parser
> > get config key list
> > decode base64 secret
> > reload
> > post event
> > using server 192.168.1.18 (192.168.1.18#953)
> > create socket
> > connect
> > rndc: connect failed: connection refused
> > "
> > The problem seems that the socket can not be connected to my own machine.
> > have closed the Windows Firewall, and 953 port shall be connected. Also,
> > have add "192.168.1.18" to the allow statement in the Control statement.
> > Anything need I do to make "rndc -s 192.168.1.18 reload" work fine?
> > Thanks a lot for your help!
> Does "netstat -an" show 192.168.1.18 listening on port 953 ?
> Post the "control" section from your config so we can help. If you dont
> want to do that, take a look at the below url for assistance.
> - Kirk