Aaron Konstam: >> Go to another machine and run dig on the contested ip address and find out >> what its name of the machine. You can also find out its machine address. Jonathan Allen: > # dig 192.168.1.6 > ; <<>> DiG 9.2.3 <<>> 192.168.1.6 > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21219 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;192.168.1.6. IN A > > ;; AUTHORITY SECTION: > . 10240 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2007121100 1800 900 604800 86400 > > ;; Query time: 34 msec > ;; SERVER: 158.152.1.58#53(158.152.1.58) > ;; WHEN: Tue Dec 11 16:05:44 2007 > ;; MSG SIZE rcvd: 104 > > I am not sure what that has told me. Only that *your* DNS server doesn't know anything about that address (there was no "ANSWER SECTION"). This means nothing in the grand scheme of things (whether something is using that address, or not). IPs don't have to be registered in a DNS server. I'd first check if it were the machine, itself, that was thinking that IP was in use. Pull out the network cable, try "ifconfig eth0 192.168.1.6" (to manually assign that address to the box) and see if it still protests that the address is in use while it's not connected to any other equipment. If you get a complaint, now, you just have to fix this machine, and you can ignore the rest of your network. There's something vaguely familiar about this issue, with some sort of phantom lingering about, but I can't recall the details. I can't recall whether it was on this list, but searching through it for that error message might be worth it. -- [tim@bigblack ~]$ uname -ipr 2.6.23.1-10.fc7 i686 i386 Using FC 4, 5, 6 & 7, plus CentOS 5. Today, it's FC7. Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
