All my queries on one machine on my network have suddenly started to resolve to 192.168.1.251.
This machine was used as the DNS server by other machines, so I noticed it as soon as it started happening and have switched all other machines to use 8.8.8.8 directly, which works.
The machines are all on a 192.168.0.x IP.
It does run dnsmasq, which I've restarted to no effect and so stopped, again, no difference.
/etc/resolv.conf did have entries for 127.0.0.1 and the router's IP, I've changed it to just contain one for 8.8.8.8 and there's nothing in /etc/hosts for a 192.168.1.251 IP.
Any ideas would be appreciated!
$ dig google.co.uk @8.8.8.8
; <<>> DiG 9.7.0-P1 <<>> google.co.uk @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49227
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;google.co.uk. IN A
;; ANSWER SECTION:
google.co.uk. 0 IN A 192.168.1.251
;; Query time: 0 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jan 6 20:22:03 2011
;; MSG SIZE rcvd: 46
$ uname -a
Linux america 2.6.32-27-generic #49-Ubuntu SMP Wed Dec 1 23:52:12 UTC 2010 i686 GNU/Linux
Edit: This seemed to start working without any sign of any changes having effected the behaviour. I'm still none the wiser, but including the files below for completeness (and in case it comes back!)
$ cat /etc/hosts
127.0.0.1 localhost
127.0.0.1 america
192.168.0.1 england
192.168.0.2 america
192.168.0.3 germany
192.168.0.4 france
192.168.0.5 sweden
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
$ cat /etc/resolv.conf
# Generated by NetworkManager
#nameserver 127.0.0.1
nameserver 8.8.8.8
#nameserver 4.2.2.2
$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat
group: compat
shadow: compat
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
cat /etc/resolv.conf
please, not that I don't trust you... but let's have the actual file./etc/hosts
and a/etc/nsswitch.conf
. though I don't think dig uses any of that, but it certainly will speak loads of information about what the system is doing. and where's mydig +trace
?