<div dir="ltr">What's in your resolv.conf file? Should be in /etc.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Sep 7, 2014 at 2:32 PM, Michael W. Hall <span dir="ltr"><<a href="mailto:hallmw@att.net" target="_blank">hallmw@att.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well that is the thing. No I have not been using it as a DNS Server.<br>
Not sure how that started doing that, but it does seem like it is DNS<br>
that is returning Jack.<br>
<br>
On Fri, 2014-09-05 at 22:09 -0500, Jared Wilkinson wrote:<br>
> I may have missed it somewhere, but are you using the Tardis server as a<br>
> DNS server?<br>
><br>
><br>
> On Fri, Sep 5, 2014 at 8:23 PM, Michael W. Hall <<a href="mailto:hallmw@att.net">hallmw@att.net</a>> wrote:<br>
><br>
> > The /etc/hosts file contains:<br>
> ><br>
> > hallmw@Tardis:~$ cat /etc/hosts<br>
> > 127.0.0.1 localhost<br>
> > 127.0.1.1 Tardis<br>
> ><br>
> > # The following lines are desirable for IPv6 capable hosts<br>
> > ::1 ip6-localhost ip6-loopback<br>
> > fe00::0 ip6-localnet<br>
> > ff00::0 ip6-mcastprefix<br>
> > ff02::1 ip6-allnodes<br>
> > ff02::2 ip6-allrouters<br>
> ><br>
> ><br>
> > On Fri, 2014-09-05 at 19:55 -0500, Jared Wilkinson wrote:<br>
> > > What does your /etc/hosts file contain?<br>
> > ><br>
> > ><br>
> > > On Fri, Sep 5, 2014 at 7:53 PM, Michael W. Hall <<a href="mailto:hallmw@att.net">hallmw@att.net</a>> wrote:<br>
> > ><br>
> > > > Any idea what file you would edit to fix that?<br>
> > > ><br>
> > > ><br>
> > > > On Thu, 2014-09-04 at 18:50 -0500, Branden Harper wrote:<br>
> > > > > There you go. There is a dns server on your local system replying<br>
> > with<br>
> > > > > that name.<br>
> > > > > On Sep 4, 2014 6:29 PM, "Michael W. Hall" <<a href="mailto:hallmw@att.net">hallmw@att.net</a>> wrote:<br>
> > > > ><br>
> > > > > > I never thought to do that. Here are the results.<br>
> > > > > > hallmw@Tardis:~$ ping jack<br>
> > > > > > PING <a href="http://jack.gateway.2wire.net" target="_blank">jack.gateway.2wire.net</a> (192.168.1.78) 56(84) bytes of data.<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=1 ttl=64 time=0.049 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=2 ttl=64 time=0.022 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=3 ttl=64 time=0.067 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=4 ttl=64 time=0.059 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=5 ttl=64 time=0.050 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=6 ttl=64 time=0.059 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=7 ttl=64 time=0.060 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=8 ttl=64 time=0.029 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=9 ttl=64 time=0.028 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=10 ttl=64 time=0.051 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=11 ttl=64 time=0.043 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=12 ttl=64 time=0.058 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=13 ttl=64 time=0.063 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=14 ttl=64 time=0.059 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=15 ttl=64 time=0.034 ms<br>
> > > > > > 64 bytes from jack (192.168.1.78): icmp_seq=16 ttl=64 time=0.059 ms<br>
> > > > > > ^C<br>
> > > > > > --- <a href="http://jack.gateway.2wire.net" target="_blank">jack.gateway.2wire.net</a> ping statistics ---<br>
> > > > > > 16 packets transmitted, 16 received, 0% packet loss, time 15001ms<br>
> > > > > > rtt min/avg/max/mdev = 0.022/0.049/0.067/0.014 ms<br>
> > > > > > hallmw@Tardis:~$ nslookup 192.168.1.78<br>
> > > > > > Server: 127.0.1.1<br>
> > > > > > Address: 127.0.1.1#53<br>
> > > > > ><br>
> > > > > > 78.1.168.192.in-addr.arpa name = jack.<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > On Thu, 2014-09-04 at 11:25 -0500, Branden Harper wrote:<br>
> > > > > > > If you do a ping to 'jack' does it work correctly? Have you<br>
> > tried<br>
> > > > > > > `nslookup jack' and `nslookup 192.168.1.78' ?<br>
> > > > > > ><br>
> > > > > > > Just a couple of things I thought of today.<br>
> > > > > > ><br>
> > > > > > ><br>
> > > > > > > On Wed, Sep 3, 2014 at 8:59 PM, Michael W. Hall <<a href="mailto:hallmw@att.net">hallmw@att.net</a>><br>
> > > > wrote:<br>
> > > > > > ><br>
> > > > > > > > After I upgraded to Ubuntu 14.04 LTS, I ssh into my desktop. I<br>
> > > > then<br>
> > > > > > > > pinged my laptop to see if the reply would say tardis. Below<br>
> > are<br>
> > > > the<br>
> > > > > > > > results. Not sure where the jack is coming from, but one reply<br>
> > > > did say<br>
> > > > > > > > Tardis.<br>
> > > > > > > ><br>
> > > > > > > > mwhall@TAZ:~$ ping tardis<br>
> > > > > > > > PING <a href="http://tardis.gateway.2wire.net" target="_blank">tardis.gateway.2wire.net</a> (192.168.1.78) 56(84) bytes of<br>
> > data.<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=1 ttl=64 time=8.31<br>
> > ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=2 ttl=64 time=13.0<br>
> > ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=3 ttl=64 time=34.4<br>
> > ms<br>
> > > > > > > > 64 bytes from Tardis.local (192.168.1.78): icmp_req=4 ttl=64<br>
> > > > time=11.1<br>
> > > > > > > > ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=6 ttl=64 time=4.25<br>
> > ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=7 ttl=64 time=6.17<br>
> > ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=8 ttl=64 time=7.28<br>
> > ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=9 ttl=64 time=3.14<br>
> > ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=10 ttl=64<br>
> > time=2.92 ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=11 ttl=64<br>
> > time=3.52 ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=12 ttl=64<br>
> > time=4.16 ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=13 ttl=64<br>
> > time=2.39 ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=14 ttl=64<br>
> > time=3.17 ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=15 ttl=64<br>
> > time=5.75 ms<br>
> > > > > > > > 64 bytes from jack (192.168.1.78): icmp_req=16 ttl=64<br>
> > time=3.03 ms<br>
> > > > > > > ><br>
> > > > > > > > On Thu, 2014-08-14 at 17:14 -0500, Michael W. Hall wrote:<br>
> > > > > > > > > My bad Bob. Laziness on my part. It is short for Raspberry<br>
> > > > Pi. The<br>
> > > > > > > > > little computer. They are awesome.<br>
> > > > > > > > ><br>
> > > > > > > > > On Thu, 2014-08-14 at 01:22 +0000, Bob Nance wrote:<br>
> > > > > > > > > > I’m afraid I don’t know what RPi is, but I would get it’s a<br>
> > > > remote<br>
> > > > > > > > ping server. If it reporting that name, it is resolving it from<br>
> > > > > > somewhere!<br>
> > > > > > > > > ><br>
> > > > > > > > > > ---<br>
> > > > > > > > > > Bob Nance<br>
> > > > > > > > > > Novation Systems<br>
> > > > > > > > > > <a href="mailto:bob.nance@novationsys.com">bob.nance@novationsys.com</a><br>
> > > > > > > > > > <a href="tel:256-534-4620" value="+12565344620">256-534-4620</a><br>
> > > > > > > > > ><br>
> > > > > > > > > > On Aug 13, 2014, at 5:36 PM, Michael W. Hall <<br>
> > <a href="mailto:hallmw@att.net">hallmw@att.net</a>><br>
> > > > > > wrote:<br>
> > > > > > > > > ><br>
> > > > > > > > > > > So you are saying tha t the RPi is putting that in the<br>
> > reply<br>
> > > > > > status?<br>
> > > > > > > > > > > That is strange, why would it do it for just my laptop?<br>
> > The<br>
> > > > > > other<br>
> > > > > > > > > > > machines have the correct name.<br>
> > > > > > > > > > ><br>
> > > > > > > > > > ><br>
> > > > > > > > > > > On Tue, 2014-08-12 at 02:58 +0000, Bob Nance wrote:<br>
> > > > > > > > > > >> I hope I understand what you’re asking. Since the ping<br>
> > > > response<br>
> > > > > > > > doesn’t carry any identifying information beyond layer 3, the<br>
> > name<br>
> > > > > > > > resolution has to be occurring on the computer reporting the<br>
> > ping<br>
> > > > > > status.<br>
> > > > > > > > Is that helpful?<br>
> > > > > > > > > > >><br>
> > > > > > > > > > >><br>
> > > > > > > > > > >> ---<br>
> > > > > > > > > > >> Bob Nance<br>
> > > > > > > > > > >> Novation Systems<br>
> > > > > > > > > > >> <a href="mailto:bob.nance@novationsys.com">bob.nance@novationsys.com</a><br>
> > > > > > > > > > >> <a href="tel:256-534-4620" value="+12565344620">256-534-4620</a><br>
> > > > > > > > > > >><br>
> > > > > > > > > > >> On Aug 11, 2014, at 9:45 PM, Michael W. Hall <<br>
> > > > <a href="mailto:hallmw@att.net">hallmw@att.net</a>><br>
> > > > > > > > wrote:<br>
> > > > > > > > > > >><br>
> > > > > > > > > > >>> Ok. I am setting up my RPi and have it working. I<br>
> > ping my<br>
> > > > > > laptop<br>
> > > > > > > > from<br>
> > > > > > > > > > >>> the RPi or any machine and in the reply it does not<br>
> > have<br>
> > > > the<br>
> > > > > > name<br>
> > > > > > > > of my<br>
> > > > > > > > > > >>> laptop. It has Jack where the name of my machine<br>
> > should<br>
> > > > be. I<br>
> > > > > > > > have<br>
> > > > > > > > > > >>> checked the hostname file and it has the name of my<br>
> > > > machine.<br>
> > > > > > > > Anyone<br>
> > > > > > > > > > >>> have an idea of where to fix that?<br>
> > > > > > > > > > >>><br>
> > > > > > > > > > >>> Thanks,<br>
> > > > > > > > > > >>> Michael<br>
> > > > > > > > > > >>><br>
> > > > > > > > > > >>> _______________________________________________<br>
> > > > > > > > > > >>> LUNA mailing list<br>
> > > > > > > > > > >>> <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > > > > > > >>> <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > > > > > > > > >><br>
> > > > > > > > > > >> _______________________________________________<br>
> > > > > > > > > > >> LUNA mailing list<br>
> > > > > > > > > > >> <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > > > > > > >> <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > > > > > > > > ><br>
> > > > > > > > > > ><br>
> > > > > > > > > > > _______________________________________________<br>
> > > > > > > > > > > LUNA mailing list<br>
> > > > > > > > > > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > > > > > > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > > > > > > > ><br>
> > > > > > > > > > _______________________________________________<br>
> > > > > > > > > > LUNA mailing list<br>
> > > > > > > > > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > > > > > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > > > _______________________________________________<br>
> > > > > > > > > LUNA mailing list<br>
> > > > > > > > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > > > > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > > > > > ><br>
> > > > > > > ><br>
> > > > > > > > _______________________________________________<br>
> > > > > > > > LUNA mailing list<br>
> > > > > > > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > > > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > > > > > ><br>
> > > > > > > -------------- next part --------------<br>
> > > > > > > An HTML attachment was scrubbed...<br>
> > > > > > > URL: <<br>
> > > > > ><br>
> > > ><br>
> > <a href="http://lunagroup.us/pipermail/luna/attachments/20140904/9eaec415/attachment.html" target="_blank">http://lunagroup.us/pipermail/luna/attachments/20140904/9eaec415/attachment.html</a><br>
> > > > > > ><br>
> > > > > > > _______________________________________________<br>
> > > > > > > LUNA mailing list<br>
> > > > > > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > > > ><br>
> > > > > ><br>
> > > > > > _______________________________________________<br>
> > > > > > LUNA mailing list<br>
> > > > > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > > > ><br>
> > > > > -------------- next part --------------<br>
> > > > > An HTML attachment was scrubbed...<br>
> > > > > URL: <<br>
> > > ><br>
> > <a href="http://lunagroup.us/pipermail/luna/attachments/20140904/bd5fd571/attachment.html" target="_blank">http://lunagroup.us/pipermail/luna/attachments/20140904/bd5fd571/attachment.html</a><br>
> > > > ><br>
> > > > > _______________________________________________<br>
> > > > > LUNA mailing list<br>
> > > > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > ><br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > LUNA mailing list<br>
> > > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> > > ><br>
> > > -------------- next part --------------<br>
> > > An HTML attachment was scrubbed...<br>
> > > URL: <<br>
> > <a href="http://lunagroup.us/pipermail/luna/attachments/20140905/27200dc6/attachment.html" target="_blank">http://lunagroup.us/pipermail/luna/attachments/20140905/27200dc6/attachment.html</a><br>
> > ><br>
> > > _______________________________________________<br>
> > > LUNA mailing list<br>
> > > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > LUNA mailing list<br>
> > <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> > <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
> ><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href="http://lunagroup.us/pipermail/luna/attachments/20140905/675a17ad/attachment.html" target="_blank">http://lunagroup.us/pipermail/luna/attachments/20140905/675a17ad/attachment.html</a>><br>
> _______________________________________________<br>
> LUNA mailing list<br>
> <a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
> <a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
<br>
<br>
_______________________________________________<br>
LUNA mailing list<br>
<a href="mailto:LUNA@lunagroup.us">LUNA@lunagroup.us</a><br>
<a href="http://lunagroup.us/mailman/listinfo/luna" target="_blank">http://lunagroup.us/mailman/listinfo/luna</a><br>
</blockquote></div><br></div>