Name resolution problems

Post #168,058 by pwhysall 8/7/04 5:04:47 AM Reply	Name resolution problems OK, so here's the network:\r\n \r\nariel <-> router <-> internet\r\n \r\nariel is on 10.200.1.50, router is at 10.200.1.1, all 16-bit netmasks. ariel provides mail/dns/dhcp/squid/yadda services for my local LAN. mail is courier, dns is maradns, dhcp is, well, dhcp.\r\n \r\nRecently (i.e. this morning), ariel stopped being able to resolve names on my local LAN. It points at itself for DNS resolution. I should point out at this juncture that ariel runs Debian unstable.\r\n \r\n \r\nThis is, I'm sure, related to the fact that due to whinging about a non existent /etc/network/ifstate file, the eth0 interface came up unbound to any IP address. If you just touch the ifstate file and then ifup the interface, it comes up fine and dandy.\r\nHowever, attempts to resolve things locally produce errors:\r\n \r\n ariel:~# host ariel\r\nariel.tranquillity.lan does not exist, try again\r\nariel:~# ping ariel\r\nPING ariel.tranquillity.lan (10.200.1.50): 56 data bytes\r\nping: sendto: Invalid argument\r\nping: wrote ariel.tranquillity.lan 64 chars, ret=-1 \r\nThe MaraDNS configuration is unchanged, and indeed works... for other boxes on the network. For example, from a Windows box:\r\n C:\\>nslookup bagpuss\r\nServer: ariel.tranquillity.lan\r\nAddress: 10.200.1.50\r\n\r\nName: bagpuss.tranquillity.lan\r\nAddress: 10.200.1.3 \r\n Questions. Why has eth0 suddenly stopped coming up automatically? Why are the ifupdown scripts suddenly whinging about ifstate? Why is maradns suddenly not serving the box it's running on if its configuration is unchanged? Why is it working for other boxes on the network? \r\n \r\nHere's some files:\r\n \r\n/etc/hosts:\r\n \r\n 127.0.0.1 localhost\r\n\r\n10.200.1.50 ariel.tranquillity.lan ariel\r\n10.200.1.50 conference.guildenstern.dyndns.org\r\n\r\n# The following lines are desirable for IPv6 capable hosts\r\n# (added automatically by netbase upgrade)\r\n\r\n::1 ip6-localhost ip6-loopback\r\nfe00::0 ip6-localnet\r\nff00::0 ip6-mcastprefix\r\nff02::1 ip6-allnodes\r\nff02::2 ip6-allrouters\r\nff02::3 ip6-allhosts \r\n/etc/resolv.conf:\r\n search tranquillity.lan\r\nnameserver 127.0.0.1 \r\n/etc/network/interfaces:\r\n # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\r\n\r\n# The loopback interface\r\nauto lo\r\niface lo inet loopback\r\n\r\n# The first network card - this entry was created during the Debian installation\r\n# (network, broadcast and gateway are optional)\r\nauto eth0\r\niface eth0 inet static\r\n address 10.200.1.50\r\n netmask 255.255.0.0\r\n network 10.200.0.0\r\n broadcast 10.200.255.255\r\n gateway 10.200.1.1 \r\n Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #168,067 by boxley 8/7/04 11:10:38 AM Reply	can you output ifconfig -a please? "delayed incessantly by people whose prevalent qualification was an excess of free-time" Philip Atkinson questions, help? [link\|mailto:pappas@catholic.org\|email pappas at catholic.org]
Post #168,068 by pwhysall 8/7/04 12:32:57 PM Reply	looks normal, eth0 has no ip address Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #168,078 by boxley 8/7/04 2:03:56 PM Reply	I wonder about your resolve.conf you have nameserver as localhost but the nameserver is listening on yer 10 net. Shouldnt also indicate that check files first then network? I am not as familiar with the Debian as I should be. [link\|http://packages.debian.org/changelogs/pool/main/i/ifupdown/ifupdown_0.6.4-4.8/changelog\|http://packages.debi...6.4-4.8/changelog] ifupdown (0.6.4-4) unstable; urgency=low * Don't delete /etc/network/ifstate every boot, just empty the file. This way people can symlink it to /var/run/ifstate if they so desire (ie, if /var is local and /etc is read-only). (Closes: Bug#103868, Bug#85206) * Explicitly set PATH in the environment, because pdksh is broken, broken I say. (Closes: Bug#83557, Bug#99444) so if yours is doing this, a package dep has been changed? thanx, bill "delayed incessantly by people whose prevalent qualification was an excess of free-time" Philip Atkinson questions, help? [link\|mailto:pappas@catholic.org\|email pappas at catholic.org]
Post #168,079 by pwhysall 8/7/04 2:07:14 PM Reply	Nameserver is listening on 0.0.0.0 Just in case :) Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #168,089 by Another Scott 8/7/04 3:28:24 PM Reply	What happened before this morning? Some things I'm sure you've considered, but on the odd chance you haven't: Was anything new from Unstable installed recently? Is ariel always on or did you notice the problem on booting it this morning? Are there any trojans/worms/etc. that attack DNS that may be acting up? As you know, things don't suddenly break for no reason. Something usually changes before the breakage is noticed. When you've checked everything and not found the problem, it's usually something you haven't checked. :-) Hope this tickles your graymatter a bit. Good luck! Cheers, Scott.

Welcome to IWETHEY!