On Fri, Jul 13, 2001 at 12:51:20PM -0700, Mike Pfleger wrote:
> On Fri, Jul 13, 2001 at 01:10:01PM -0600, Jimmy Richards wrote:
> <SNIP>
> >     Try   dig -x 192.168.1.45
> 
> Hi Jim.
> 
> OK.  Here's the spew:
> 
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55359
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;45.1.168.192.in-addr.arpa.     IN      PTR
> 
> ;; AUTHORITY SECTION:
> 168.192.IN-ADDR.ARPA.   10590   IN      SOA     blackhole.isi.edu. 
> bmanning.isi.edu. 19971802 10800 900 604800 86400
> 
> ;; Query time: 65 msec
> ;; SERVER: 24.64.223.195#53(24.64.223.195)
> ;; WHEN: Fri Jul 13 12:43:32 2001
> ;; MSG SIZE  rcvd: 125
> 
> It appears that the first nameserver in resolv.conf is queried about
> this.  This is what I suspected.  Since I am using dhcp-client on
> this workstation, and a fireplug firewall, what do I need to do to
> /etc/hosts to make it reflect the state of ifconfig (see below)?
> 
> eth0  Link encap:Ethernet  HWaddr 00:A0:CC:E5:FA:7C  
>       inet addr:192.168.1.45  Bcast:192.168.1.255  Mask:255.255.255.0
>       UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>       RX packets:6503 errors:0 dropped:0 overruns:0 frame:0
>       TX packets:6990 errors:0 dropped:0 overruns:0 carrier:0
>       collisions:0 txqueuelen:100 
>       RX bytes:3417730 (3.2 Mb)  TX bytes:725129 (708.1 Kb)
>       Interrupt:12 Base address:0xb000 
> 
> lo    Link encap:Local Loopback  
>       inet addr:127.0.0.1  Mask:255.0.0.0
>       UP LOOPBACK RUNNING  MTU:16436  Metric:1
>       RX packets:2827 errors:0 dropped:0 overruns:0 frame:0
>       TX packets:2827 errors:0 dropped:0 overruns:0 carrier:0
>       collisions:0 txqueuelen:0 
>       RX bytes:675627 (659.7 Kb)  TX bytes:675627 (659.7 Kb)
> 
> TIA,
> Mike

My last message crossed with this one, I didn't realize you'd discovered
that the address was your machine's. If you can rely on keeping the
address, you can put whatever you like in /etc/hosts

192.168.1.45    debiansystem

But this isn't the answer, the answer is to properly configure the
service that's causing the error, probably by having it reference
'localhost'.

HTH, Paul

Reply via email to