{"id":1098,"date":"2012-08-21T10:33:06","date_gmt":"2012-08-21T08:33:06","guid":{"rendered":"http:\/\/www.dotmana.com\/weblog\/?p=1098"},"modified":"2012-08-21T10:33:06","modified_gmt":"2012-08-21T08:33:06","slug":"hostname-name-or-service-not-known","status":"publish","type":"post","link":"http:\/\/www.dotmana.com\/weblog\/2012\/08\/hostname-name-or-service-not-known\/","title":{"rendered":"hostname : name or service not known"},"content":{"rendered":"

Pour ceux qui gal\u00e8rent avec leur hostname en FQDN, voici le tuto \u00e0 suivre<\/a> :<\/p>\n

\n

Getting the FQDN to work properly can be a b*tch. \ud83d\ude09<\/p>\n

Basically, for the FQDN resolution to work correctly, three (or four)
\n things need to play together. That’s the files \/etc\/hostname,
\n\/etc\/hosts, \/etc\/resolv.conf and your external nameserver (provided by
\nyour hoster e.g.).<\/p>\n

Let’s say your server’s hostname is “lyra” and its already
\nestablished and externally resolvable domain name is “tianet.de”. Let’s
\nfurther say that lyra’s IP is 46.4.181.243, and the nameserver that
\nforwards requests to the outside has the IP 46.4.181.241 (real-life
\nexample from my experimental Virtualmin VM).<\/p>\n

Then the contents need to be as follows:<\/p>\n

\/etc\/hostname<\/code><\/p>\n

\n
lyra<\/pre>\n<\/div>\n
\/etc\/hosts<\/code><\/p>\n
\n
127.0.0.1       localhost\n46.4.181.243    lyra.tianet.de lyra<\/pre>\n<\/div>\n
(Note that I have both the FQDN and the standalone hostname there.)<\/p>\n
\/etc\/resolv.conf<\/code><\/p>\n
\n
nameserver 46.4.181.241\ndomain tianet.de<\/pre>\n<\/div>\n
After setting these contents, it might be helpful\/required to reboot the machine or execute \/etc\/init.d\/networking restart<\/code>, though usually that’s not necessary.<\/p>\n
hostname<\/code> should then reply with “lyra”, and hostname -f<\/code> with “lyra.tianet.de”.<\/p>\n
If you still have trouble then, you can additionally check the file \/etc\/nsswitch.conf<\/code> which tells the system which facilities to consult for resolving various stuff. You should have a line like this there:<\/p>\n
\n
hosts: files dns<\/pre>\n<\/div>\n
If it’s missing or deviating, edit it to this.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"
Pour ceux qui gal\u00e8rent avec leur hostname en FQDN, voici le tuto \u00e0 suivre : Getting the FQDN to work properly can be a b*tch. \ud83d\ude09 Basically, for the FQDN resolution to work correctly, three (or four) things need to … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26,14],"tags":[],"class_list":["post-1098","post","type-post","status-publish","format-standard","hentry","category-linux","category-work"],"_links":{"self":[{"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/posts\/1098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/comments?post=1098"}],"version-history":[{"count":2,"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/posts\/1098\/revisions"}],"predecessor-version":[{"id":1100,"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/posts\/1098\/revisions\/1100"}],"wp:attachment":[{"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/media?parent=1098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/categories?post=1098"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.dotmana.com\/weblog\/wp-json\/wp\/v2\/tags?post=1098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}