nmap won't recognize a hostname on my local area network












2















Scanning the machine on the LAN with my laptop, I got this:



gabriele @ osiris { ~ } [ Tue Oct 07 ] [ 08:49 PM]
nmap -sP 192.168.1.236

Starting Nmap 6.40 ( http://nmap.org ) at 2014-10-07 20:50 CEST
Nmap scan report for ---.homenet.telecomitalia.it (192.168.1.236)
Host is up (0.0044s latency).
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds


nmap won't recognize the nostname, putting—in place of "mercury" and I assume is not a problem of nmap because it doesn't even access in this way:



root@mercury


when I changed the hostname I follow these steps



sudo nano /etc/hostname


and I wrote a single line with "mercury", then:



sudo nano /etc/hosts


with this configuration:



127.0.0.1       localhost
127.0.1.1 mercury localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters


and finally:



sudo /etc/init.d/hostname.sh start


am I doing something wrong?










share|improve this question
















bumped to the homepage by Community 33 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • That's probably the result of the reverse DNS lookup. What does host 192.168.1.236 print?

    – Martin von Wittich
    Oct 7 '14 at 19:07











  • 236.1.168.192.in-addr.arpa domain name pointer ---.homenet.telecomitalia.it.

    – Gabriele Salvatori
    Oct 7 '14 at 19:10











  • Yep, it looks like the ---.homenet.telecomitalia.it is coming from your DNS server. If that is your local router provided by your ISP, have a look in the web interface - there could be a way to rename that entry.

    – Martin von Wittich
    Oct 7 '14 at 21:18
















2















Scanning the machine on the LAN with my laptop, I got this:



gabriele @ osiris { ~ } [ Tue Oct 07 ] [ 08:49 PM]
nmap -sP 192.168.1.236

Starting Nmap 6.40 ( http://nmap.org ) at 2014-10-07 20:50 CEST
Nmap scan report for ---.homenet.telecomitalia.it (192.168.1.236)
Host is up (0.0044s latency).
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds


nmap won't recognize the nostname, putting—in place of "mercury" and I assume is not a problem of nmap because it doesn't even access in this way:



root@mercury


when I changed the hostname I follow these steps



sudo nano /etc/hostname


and I wrote a single line with "mercury", then:



sudo nano /etc/hosts


with this configuration:



127.0.0.1       localhost
127.0.1.1 mercury localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters


and finally:



sudo /etc/init.d/hostname.sh start


am I doing something wrong?










share|improve this question
















bumped to the homepage by Community 33 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • That's probably the result of the reverse DNS lookup. What does host 192.168.1.236 print?

    – Martin von Wittich
    Oct 7 '14 at 19:07











  • 236.1.168.192.in-addr.arpa domain name pointer ---.homenet.telecomitalia.it.

    – Gabriele Salvatori
    Oct 7 '14 at 19:10











  • Yep, it looks like the ---.homenet.telecomitalia.it is coming from your DNS server. If that is your local router provided by your ISP, have a look in the web interface - there could be a way to rename that entry.

    – Martin von Wittich
    Oct 7 '14 at 21:18














2












2








2








Scanning the machine on the LAN with my laptop, I got this:



gabriele @ osiris { ~ } [ Tue Oct 07 ] [ 08:49 PM]
nmap -sP 192.168.1.236

Starting Nmap 6.40 ( http://nmap.org ) at 2014-10-07 20:50 CEST
Nmap scan report for ---.homenet.telecomitalia.it (192.168.1.236)
Host is up (0.0044s latency).
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds


nmap won't recognize the nostname, putting—in place of "mercury" and I assume is not a problem of nmap because it doesn't even access in this way:



root@mercury


when I changed the hostname I follow these steps



sudo nano /etc/hostname


and I wrote a single line with "mercury", then:



sudo nano /etc/hosts


with this configuration:



127.0.0.1       localhost
127.0.1.1 mercury localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters


and finally:



sudo /etc/init.d/hostname.sh start


am I doing something wrong?










share|improve this question
















Scanning the machine on the LAN with my laptop, I got this:



gabriele @ osiris { ~ } [ Tue Oct 07 ] [ 08:49 PM]
nmap -sP 192.168.1.236

Starting Nmap 6.40 ( http://nmap.org ) at 2014-10-07 20:50 CEST
Nmap scan report for ---.homenet.telecomitalia.it (192.168.1.236)
Host is up (0.0044s latency).
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds


nmap won't recognize the nostname, putting—in place of "mercury" and I assume is not a problem of nmap because it doesn't even access in this way:



root@mercury


when I changed the hostname I follow these steps



sudo nano /etc/hostname


and I wrote a single line with "mercury", then:



sudo nano /etc/hosts


with this configuration:



127.0.0.1       localhost
127.0.1.1 mercury localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters


and finally:



sudo /etc/init.d/hostname.sh start


am I doing something wrong?







shell networking nmap lan






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 7 '14 at 20:48







Gabriele Salvatori

















asked Oct 7 '14 at 19:06









Gabriele SalvatoriGabriele Salvatori

1114




1114





bumped to the homepage by Community 33 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 33 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • That's probably the result of the reverse DNS lookup. What does host 192.168.1.236 print?

    – Martin von Wittich
    Oct 7 '14 at 19:07











  • 236.1.168.192.in-addr.arpa domain name pointer ---.homenet.telecomitalia.it.

    – Gabriele Salvatori
    Oct 7 '14 at 19:10











  • Yep, it looks like the ---.homenet.telecomitalia.it is coming from your DNS server. If that is your local router provided by your ISP, have a look in the web interface - there could be a way to rename that entry.

    – Martin von Wittich
    Oct 7 '14 at 21:18



















  • That's probably the result of the reverse DNS lookup. What does host 192.168.1.236 print?

    – Martin von Wittich
    Oct 7 '14 at 19:07











  • 236.1.168.192.in-addr.arpa domain name pointer ---.homenet.telecomitalia.it.

    – Gabriele Salvatori
    Oct 7 '14 at 19:10











  • Yep, it looks like the ---.homenet.telecomitalia.it is coming from your DNS server. If that is your local router provided by your ISP, have a look in the web interface - there could be a way to rename that entry.

    – Martin von Wittich
    Oct 7 '14 at 21:18

















That's probably the result of the reverse DNS lookup. What does host 192.168.1.236 print?

– Martin von Wittich
Oct 7 '14 at 19:07





That's probably the result of the reverse DNS lookup. What does host 192.168.1.236 print?

– Martin von Wittich
Oct 7 '14 at 19:07













236.1.168.192.in-addr.arpa domain name pointer ---.homenet.telecomitalia.it.

– Gabriele Salvatori
Oct 7 '14 at 19:10





236.1.168.192.in-addr.arpa domain name pointer ---.homenet.telecomitalia.it.

– Gabriele Salvatori
Oct 7 '14 at 19:10













Yep, it looks like the ---.homenet.telecomitalia.it is coming from your DNS server. If that is your local router provided by your ISP, have a look in the web interface - there could be a way to rename that entry.

– Martin von Wittich
Oct 7 '14 at 21:18





Yep, it looks like the ---.homenet.telecomitalia.it is coming from your DNS server. If that is your local router provided by your ISP, have a look in the web interface - there could be a way to rename that entry.

– Martin von Wittich
Oct 7 '14 at 21:18










1 Answer
1






active

oldest

votes


















0














change ur /etc/hosts file from




127.0.0.1 localhost



127.0.1.1 mercury localhost




to:




127.0.0.1 localhost



192.168.1.236 mercury




once you do that, "ping mercury" or "nmap mercury" should work, and the inverse, "nmap 192.168.1.236" should then show the hostname associated with that IP in /etc/hosts, in the nmap report output






share|improve this answer
























  • Seems doesn't work.

    – Gabriele Salvatori
    Oct 7 '14 at 19:35













  • paste ur output... paste ur hosts file

    – nandoP
    Oct 9 '14 at 20:49











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f159886%2fnmap-wont-recognize-a-hostname-on-my-local-area-network%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














change ur /etc/hosts file from




127.0.0.1 localhost



127.0.1.1 mercury localhost




to:




127.0.0.1 localhost



192.168.1.236 mercury




once you do that, "ping mercury" or "nmap mercury" should work, and the inverse, "nmap 192.168.1.236" should then show the hostname associated with that IP in /etc/hosts, in the nmap report output






share|improve this answer
























  • Seems doesn't work.

    – Gabriele Salvatori
    Oct 7 '14 at 19:35













  • paste ur output... paste ur hosts file

    – nandoP
    Oct 9 '14 at 20:49
















0














change ur /etc/hosts file from




127.0.0.1 localhost



127.0.1.1 mercury localhost




to:




127.0.0.1 localhost



192.168.1.236 mercury




once you do that, "ping mercury" or "nmap mercury" should work, and the inverse, "nmap 192.168.1.236" should then show the hostname associated with that IP in /etc/hosts, in the nmap report output






share|improve this answer
























  • Seems doesn't work.

    – Gabriele Salvatori
    Oct 7 '14 at 19:35













  • paste ur output... paste ur hosts file

    – nandoP
    Oct 9 '14 at 20:49














0












0








0







change ur /etc/hosts file from




127.0.0.1 localhost



127.0.1.1 mercury localhost




to:




127.0.0.1 localhost



192.168.1.236 mercury




once you do that, "ping mercury" or "nmap mercury" should work, and the inverse, "nmap 192.168.1.236" should then show the hostname associated with that IP in /etc/hosts, in the nmap report output






share|improve this answer













change ur /etc/hosts file from




127.0.0.1 localhost



127.0.1.1 mercury localhost




to:




127.0.0.1 localhost



192.168.1.236 mercury




once you do that, "ping mercury" or "nmap mercury" should work, and the inverse, "nmap 192.168.1.236" should then show the hostname associated with that IP in /etc/hosts, in the nmap report output







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 7 '14 at 19:29









nandoPnandoP

35613




35613













  • Seems doesn't work.

    – Gabriele Salvatori
    Oct 7 '14 at 19:35













  • paste ur output... paste ur hosts file

    – nandoP
    Oct 9 '14 at 20:49



















  • Seems doesn't work.

    – Gabriele Salvatori
    Oct 7 '14 at 19:35













  • paste ur output... paste ur hosts file

    – nandoP
    Oct 9 '14 at 20:49

















Seems doesn't work.

– Gabriele Salvatori
Oct 7 '14 at 19:35







Seems doesn't work.

– Gabriele Salvatori
Oct 7 '14 at 19:35















paste ur output... paste ur hosts file

– nandoP
Oct 9 '14 at 20:49





paste ur output... paste ur hosts file

– nandoP
Oct 9 '14 at 20:49


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f159886%2fnmap-wont-recognize-a-hostname-on-my-local-area-network%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

宮崎県

濃尾地震

シテ島