|
Thu, 25 Mar 2010 14:19:18 -0500 <ron.l.johnson@cox.net> wrote: > > On 2010-03-25 13:54, Mike Viau wrote: > > Hello debian-users, > > > > I have run into an interesting issue with the DNS resolution on only > > _one_ of my debian lenny systems on my network. > > > > I have confirmed that this system has working network connectivity but I > > would like to restore the ability to query DNS records from my local DNS > > server which is also in my case my network gateway. Additionally I can > > ssh into the system easily while connected to the same local network > > 10.254.2.0/24 > > > > The working (as in with other systems on my network) DNS and router is > > at 10.254.2.254/24. The IP statically set for the debian system is > > 10.254.2.1/24 > > How is this machine configured differently than the other two? > This machine is configured statically, while the others get their IP from DHCP, however when they are set statically they work fine too. > > Some info from this AMD64 architecture system is below. > > > > root@localhost:~# cat /etc/debian_version > > 5.0.4 > > > > > > root@localhost:~# cat /etc/resolv.conf > > domain site > > search site > > Why these two lines? > > Why *before* the nameserver? > I never changed the /etc/resolv.conf after running dhclient br200, so its my quess that this is the dhclient behaviour. > > nameserver 10.254.2.254 > > > > How are you populating this file? > dhclient behaviour. > > root@localhost:~# route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use > > Iface > > 10.254.2.0 * 255.255.255.0 U 0 0 0 > > br200 > > default 10.254.2.254 0.0.0.0 UG 0 0 0 > > br200 > > > > > > Snippet from /etc/network/interfaces: > > > > # LAN bridge > > iface eth1.200 inet manual > > auto br200 > > iface br200 inet static > > address 10.254.2.1 > > Why the non-standard interface name? > This interface is bridged to VLAN. That way my host machine can run a 802.1q trunk to my network switch while remaining communicating with untagged machines on the vlan ID 200. > > network 10.254.2.0 > > netmask 255.255.255.0 > > broadcast 10.254.2.255 > > gateway 10.254.2.254 > > bridge-ports eth1.200 > > > > Why not add a dns-nameservers to "iface br200"? > I am going to try this next ;) > > root@localhost:~# ping 66.249.90.104 (a google IP beyond local router) > > PING 66.249.90.104 (66.249.90.104) 56(84) bytes of data. > > 64 bytes from 66.249.90.104: icmp_seq=1 ttl=53 time=25.7 ms > > 64 bytes from 66.249.90.104: icmp_seq=2 ttl=53 time=24.3 ms > > 64 bytes from 66.249.90.104: icmp_seq=3 ttl=53 time=25.0 ms > > > > Can you ping 10.254.2.254? I'm sure you can, but just asking. > Yes and your correct as well. > > root@localhost:~# traceroute 66.249.90.104 > > traceroute to 66.249.90.104 (66.249.90.104), 30 hops max, 40 byte packets > > 1 * * * > > 2 * * * > > Try mtr-tiny instead. I am unable to make a connection to "http.us.debian.org." It worth mentioning that I was able to update this system from the debian repos previously, but I am unware of what I might have done to break the DNS functionality. > > > -- > "History does not long entrust the care of freedom to the weak > or the timid." Dwight Eisenhower > > > -- > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > Archive: http://lists.debian.org/[🔎] 4BABB736.909@cox.net > -M Live connected with Messenger on your phone Learn more. |