On Sat, 2007-10-20 at 23:52 +0930, Tim wrote: > On Sat, 2007-10-20 at 08:53 -0500, Aaron Konstam wrote: > > There is something missing in what you say. I assumed we were trying > > to decide if my personal router is capable of being a DNS server. So > > the first address I placed in the dig command was the address of my > > router. Clearly my router is supplying the addresses to my machines > > through DNS. At least I think that is clear. But no ANSWER SECTION > > appears. > > Syntax dig <address to be resolved> @<address of the resolver to use> > > e.g. My router's DNS server is at 192.168.1.254 and I'll ask it to > tell > me the IP for google. Command example: dig google.com @192.168.1.254 > > If my router had something that responds to DNS queries, and it can > give > me an answer for my query, I'll get a result from dig like this: Tim, I am so embarrassed that I wish I could send this to you personally. But since I can't I will embarrass myself for the second time in a month with what must be a bad wiring in my brain. You said DNS and my brain translated that into DHCP. I clearly need too go in for a memory upgrade. I am sorry I made such a thing of this when you were obviously right all along. -- ======================================================================= Yow! I just went below the poverty line! ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx
