Re: Re: Re: F8 Network Woe
- From: Aaron Konstam <akonstam@xxxxxxxxxxxxx>
- Date: Tue, 11 Dec 2007 15:22:14 -0600
On Tue, 2007-12-11 at 16:07 +0000, Jonathan Allen wrote:
On Tue, Dec 11, 2007 at 09:46:34AM -0600, Aaron Konstam wrote:You are right. I sent you to the wrong command.
Did you not say you had stopped NM from running.
Yes I did and NM is not running.
Go to another machine and run dig on the contested ip address and find out
what its name of the machine. You can also find out its machine address.
# dig 192.168.1.6
; <<>> DiG 9.2.3 <<>> 192.168.1.6
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21219
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.168.1.6. IN A
;; AUTHORITY SECTION:
. 10240 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2007121100 1800 900 604800 86400
;; Query time: 34 msec
;; SERVER: 158.152.1.58#53(158.152.1.58)
;; WHEN: Tue Dec 11 16:05:44 2007
;; MSG SIZE rcvd: 104
I am not sure what that has told me.
Jonathan
host 192.168.1.6
or
nslookup 192.168.1.6
What we are looking foe is something like:
[akonstam@cyrus ~]$ host 131.194.71.168
168.71.194.131.in-addr.arpa domain name pointer cs.trinity.edu.
168.71.194.131.in-addr.arpa domain name pointer sol.cs.trinity.edu.
or
[akonstam@cyrus ~]$ nslookup 131.194.71.168
Server: 192.168.1.254
Address: 192.168.1.254#53
Non-authoritative answer:
168.71.194.131.in-addr.arpa name = cs.trinity.edu.
168.71.194.131.in-addr.arpa name = sol.cs.trinity.edu.
which would tell us the name of the machine using that ip address.
--
=======================================================================
Shannon's Observation: Nothing is so frustrating as a bad situation that
is beginning to improve.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- Follow-Ups:
- Re: Re: Re: F8 Network Woe
- From: Jonathan Allen
- Re: Re: Re: F8 Network Woe
- References:
- Re: Re: Re: F8 Network Woe
- From: mike cloaked
- Re: Re: Re: F8 Network Woe
- From: Jonathan Allen
- Re: Re: Re: F8 Network Woe
- From: Aaron Konstam
- Re: Re: Re: F8 Network Woe
- From: Jonathan Allen
- Re: Re: Re: F8 Network Woe
- Prev by Date: Re: Update problems!
- Next by Date: Re: exe process: what is this?
- Previous by thread: Re: Re: Re: F8 Network Woe
- Next by thread: Re: Re: Re: F8 Network Woe
- Index(es):
Relevant Pages
|