On 1/2/2018 8:16 AM, john doe wrote:
On 1/2/2018 8:01 AM, Tom Furie wrote:On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote:My default route is not 192.168.1.1 and host(1) gives me that same error.What the error actually means is that there is no reverse DNS resolution for that IP address, in other words the IP address cannot be resolved to its hostname. It has nothing at all to do with routing.The OP has said that he want it to get the hostname of his upstream router/gateway. 'ip -r r' will show the FQDN of his default route (192.168.1.1) in that case.
Rereading the all conversation I should have said to "David Wright <deblis@lionunicorn.co.uk>" that the error:
$ host 192.168.1.1 Host 1.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN) Meens that there is no hostname associated with that ip. But in the case of the OP it should work. -- John Doe