Re (4): name - address resolution
Andrei, * Date: Wed, 24 Feb 2010 00:07:09 +0200 you wrote, Try adding a line like xxx.xxx.xxx.xxx joule.invalid joule Right oh. That works. pe...@joule:~$ cat /etc/hosts | grep 172.23.3.1 172.23.3.1 joule.invalid joule pe...@joule:~$ host joule joule has address 172.23.3.1 pe...@joule:~$ host joule.invalid joule.invalid has address 172.23.3.1 But until about a month back that was unnecessary. host joule would report the address which DHCP had assigned to the interface connected to the ISP. Is this a new normal behaviour? Is something broken? I don't recall your network topology In case anyone is interested. http://carnot.yi.org/NetworksPage.html A diagram is cited there. Thanks, ... Peter E. -- Google pathology workshop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056419.36372.353...@cantor.invalid
Re: Re (2): name - address resolution
On Mon,22.Feb.10, 09:56:36, peasth...@shaw.ca wrote: Andrei, Date: Sun, 21 Feb 2010 03:35:43 +0200 andreimpope...@gmail.co wrote, What does your /etc/hosts file look like? Now visible. http://carnot.yi.org/joule.hosts With the link to the ISP configured by dhcp, the only address for joule is the good old 127.0.0.1. Try adding a line like xxx.xxx.xxx.xxx joule.invalid joule with the proper IP (sorry, I don't recall you network topology) and restart dnsmasq. This works for me on several machines with dnsmasq as DNS cacher/DHCP server. Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re (2): name - address resolution
Andrei, Date: Sun, 21 Feb 2010 03:35:43 +0200 andreimpope...@gmail.co wrote, What does your /etc/hosts file look like? Now visible. http://carnot.yi.org/joule.hosts With the link to the ISP configured by dhcp, the only address for joule is the good old 127.0.0.1. Incidentally, is there a reason for 127.0.0.1 to be in /etc/hosts rather than in a *.h file? Regards,... Peter E. -- Google pathology workshop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056406.40484.374...@heaviside.invalid
name - address resolution
I'm reposting this question with answers to questions from Alex Samad organized better. This problem appeared after an update of Squeeze on February 7 or 8. Joule is a router with network access by a dhcp configured link. dnsmasq and resolvconf worked for months with no problem. Now the machine doesn't resolve its own name. Other names inside and outside the LAN are still resolved. pe...@joule:~$ cat /etc/hostname joule pe...@joule:~$ host joule Host joule not found: 3(NXDOMAIN) pe...@joule:~$ host joule.invalid Host joule.invalid not found: 3(NXDOMAIN) pe...@joule:~$ host dalton dalton has address 142.103.107.137 This is the last message to the console at startup. apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName Also I wonder whether a problem with qpopper derives from this name-address problem. Results are the same with kernels 2.6.30-2-686 and 2.6.32-trunk-686. Date: Tue, 16 Feb 2010 18:04:53 +1100, Alex Samad wrote, as I presume you are on joule and it has dnsmasq + resolvconf installed on it. Yes. as can you as cat /etc/resolv.conf* pe...@joule:~$ cat /etc/resolv.conf* # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search pi.shawcable.net as kill -SIGUSR1 $(pidof dnsmasq) ; tail -n 40 /var/log/syslog | grep dnsmas | tail -n 4 joule:/home/peter# kill -SIGUSR1 $(pidof dnsmasq) ; tail -n 40 /var/log/syslog | grep dnsmas | tail -n 4 Feb 20 16:01:31 joule dnsmasq[2070]: queries forwarded 29, queries answered loca lly 24 Feb 20 16:01:31 joule dnsmasq[2070]: server 64.59.160.13#53: queries sent 12, re tried or failed 0 Feb 20 16:01:31 joule dnsmasq[2070]: server 64.59.160.15#53: queries sent 26, re tried or failed 0 Feb 20 16:01:31 joule dnsmasq[2070]: server 64.59.144.19#53: queries sent 15, re tried or failed 0 as and maybe cat dnsmasq.conf Visible here. http://carnot.yi.org/joule.dnsmasq.conf It's the installed default with a few comment lines added. Any further ideas? Thanks, ... Peter E. -- Google pathology workshop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056404.70261.629...@heaviside.invalid
Re: name - address resolution
On Sat,20.Feb.10, 17:09:53, peasth...@shaw.ca wrote: I'm reposting this question with answers to questions from Alex Samad organized better. This problem appeared after an update of Squeeze on February 7 or 8. Joule is a router with network access by a dhcp configured link. dnsmasq and resolvconf worked for months with no problem. Now the machine doesn't resolve its own name. Other names inside and outside the LAN are still resolved. What does your /etc/hosts file look like? Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re (2): name - address resolution
Date: Tue, 16 Feb 2010 18:04:53 +1100, Alex Samad wrote, as I presume you are on joule and it has dnsmasq + resolvconf installed on it. Yes. In this instance, telneted to Joule via an openvpn tunnel. as can you as cat /etc/resolv.conf* Last login: Mon Feb 15 17:23:57 PST 2010 on tty1 Linux joule 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 ... joule:/home/peter# cat /etc/resolv.conf* # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search pi.shawcable.net as kill -SIGUSR1 $(pidof dnsmasq) ; tail -n 40 /var/log/syslog | grep dnsmas | tail -n 4 joule:/home/peter# kill -SIGUSR1 $(pidof dnsmasq) ; tail -n 40 /var/log/syslog | grep dnsmas | tail -n 4 Feb 16 15:54:38 joule dnsmasq[1843]: queries forwarded 1939, queries answered locally 1832 Feb 16 15:54:38 joule dnsmasq[1843]: server 64.59.160.13#53: queries sent 1907, retried or failed 3 Feb 16 15:54:38 joule dnsmasq[1843]: server 64.59.160.15#53: queries sent 1915, retried or failed 3 Feb 16 15:54:38 joule dnsmasq[1843]: server 64.59.144.19#53: queries sent 1879, retried or failed 0 as and maybe cat dnsmasq.conf joule:/home/peter# cat dnsmasq.conf cat: dnsmasq.conf: No such file or directory joule:/home/peter# The failed queries could be Joule asking for his own address; but this should not happen. Thanks, ... Peter E. -- Google pathology workshop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056400.66350.640...@cantor.invalid
correction for dnsmasq.conf; was Re (2): name - address resolution
Alex, as ... and maybe cat dnsmasq.conf Sorry; I was halucinating in the previous reply. The dnsmasq.conf on Joule is now visible here. http://carnot.yi.org/joule.dnsmasq.conf Regards,... Peter E. -- Google pathology workshop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056400.71032.697...@cantor.invalid
name - address resolution
This is another problem which appeared after an update of Squeeze on February 7 or 8. Joule is a router. dnsmasq and resolvconf have worked for months with no problem. Now the machine doesn't recognize its local name. Other names inside and outside the LAN are still resolved. For example, telnet://pe...@172.23.5.1 and telnet://pe...@joule.yi.org work but telnet://pe...@joule and telnet://pe...@joule.invalid fail. telnet://pe...@172.23.5.1 gets these lines in the syslog. Feb 15 12:47:10 joule in.telnetd[2885]: connect from 172.23.5.2 (172.23.5.2) Feb 15 12:47:10 joule telnetd[2885]: doit: getaddrinfo: Name or service not known This is the last message to the console at startup. apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName Also I wonder whether a problem with qpopper derives from this name problem. Results are the same with kernels 2.6.30-2-686 and 2.6.32-trunk-686. /etc/hosts has the name of the machine. Where is the domain name recorded? Why does this problem appear now? Thanks, ... Peter E. -- Google pathology workshop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056399.62578.567...@heaviside.invalid
correction, Re: name - address resolution
The third to last sentence should have been, /etc/hostname has the name of the machine. ... Peter E. -- Google pathology workshop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056399.63286.567...@heaviside.invalid
Re: name - address resolution
On Mon, Feb 15, 2010 at 03:17:50PM -0700, peasth...@shaw.ca wrote: This is another problem which appeared after an update of Squeeze on February 7 or 8. Joule is a router. dnsmasq and resolvconf have worked for months with no problem. Now the machine doesn't recognize its local name. Other names inside and outside the LAN are still resolved. For example, telnet://pe...@172.23.5.1 and telnet://pe...@joule.yi.org work but telnet://pe...@joule and telnet://pe...@joule.invalid fail. telnet://pe...@172.23.5.1 gets these lines in the syslog. Feb 15 12:47:10 joule in.telnetd[2885]: connect from 172.23.5.2 (172.23.5.2) Feb 15 12:47:10 joule telnetd[2885]: doit: getaddrinfo: Name or service not known This is the last message to the console at startup. apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName Also I wonder whether a problem with qpopper derives from this name problem. Results are the same with kernels 2.6.30-2-686 and 2.6.32-trunk-686. /etc/hosts has the name of the machine. Where is the domain name recorded? Why does this problem appear now? I presume you are on joule and it has dnsmasq + resolvconf installed on it. can you cat /etc/resolv.conf* kill -SIGUSR1 $(pidof dnsmasq) ; tail -n 40 /var/log/syslog | grep dnsmas | tail -n 4 and maybe cat dnsmasq.conf Thanks, ... Peter E. -- The United States and Russia are in the midst of transformationed relationship that will yield peace and progress. - George W. Bush 11/13/2001 Washington, DC signature.asc Description: Digital signature
