The response from the network folks was interesting: "I wouldn't have thought of this if you hadn't mentioned samba, but it looks like the name got shoved into WINS somehow. It is not listed in the DNS server. To test, I fired up a packet capture before I tried ping, so I could see how my host learned about the name: Source Destination Proto Info 192.168.37.13 205.235.227.50 DNS Standard query A linux60.stlouiscity.com 205.235.227.50 192.168.37.13 DNS Standard query response, No such name 192.168.37.13 205.235.227.52 NBNS Name query NB LINUX60<00> 205.235.227.52 192.168.37.13 NBNS Name query response NB 192.168.193.160 192.168.37.13 192.168.193.160 ICMP Echo (ping) request 192.168.193.160 192.168.37.13 ICMP Echo (ping) reply
At some point, it must have registered itself within WINS, or WINS found out about it and made note." So, given that I didn't knowing try to use WINS (but I might have), and I didn't install or bring up the DNS server, which, per the doc, would have added the DNS entry, what might have caused this automagically process? Also, given that LINUX61 was created the same way, and a "ping linux61" still fails? Thanks Tom Duerbusch THD Consulting >>> Mark Perry <[EMAIL PROTECTED]> 7/3/2008 6:27 AM >>> Tom Duerbusch wrote: > Really, really dumb question..... > > What would make a DNS server automagically add an entry into its list? > If you are using DHCP and the DHCP Server is configured to update the associated DNS, that would do it "automagically". Discuss with your network admin. mark ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
