[plug] DNS problem has me stumped

[Peter Weatherall]

sol wrote:

>>Open two terminals and "tail -f /var/log/messages" in one.
>>
>>And "service named restart" in the other.
>>
>>See if named complains about anything in messages on a restart.
>>    
>>
>
>Nothing. :-(   (Actually I had to /etc/init.d/bind9 restart cos service named 
>restart didn't work. I think this is a debian thing.)
>Come to think of it Telstra were digging around the wires only a couple of 
>days before. But if it were hardware I wouldn't be able to ssh to the 
>machine.
>Awww. This is too complicated. I'm taking my ball and going home. :-(
>
>sol
>ps: Thanks Ben. 
>
>
>
>
>On Fri, 11 Apr 2003 11:12 pm, Ben Jensz wrote:
>  
>
>>Sol wrote:
>>    
>>
>>>Thankyou for your reply Peter.
>>>"ps aux | grep named" gets:
>>>root	164	0.0	0.9	10204	2344	?	S	16:43	0:00	/usr/sbin/named
>>>root	166	0.0	0.9	10204	2344	?	S	16:43	0:00	/usr/sbin/named
>>>root	167	0.0	0.9	10204	2344	?	S	16:43	0:00	/usr/sbin/named
>>>root	168	0.0	0.9	10204	2344	?	S	16:43	0:00	/usr/sbin/named
>>>root	169	0.0	0.9	10204	2344	?	S	16:43	0:00	/usr/sbin/named
>>>root	1812	0.0	0.1	1336	468	pts/1	S	22:32	0:00	grep named
>>>
>>>/var/log/messages had nothing of note to tell me (except a complaint about
>>>xfs which I didn't realise was a problem). I just read the manpage for
>>>named to work out what that was all about. :-) I've still no idea what
>>>the above message is all about. What do these tea leaves have to tell us?
>>>
>>>Cheers,
>>>sol
>>>      
>>>
>
>
>  
>
OTH ,another thing to check is whether your firewall software is 
blocking ports associated with named i.e UDP port 53 and some others 
I've forgotten
Regards