[Cialug] DNS Reverse Lookup

[Matthew Lechleider]

I received the same response.

Is there a standard response for reverse lookups on internally reserved 
address space?

Does your computer know to look at your local namserver and not a public 
Internet nameserver?


Tom Sellers wrote:
> Here is the response to using the command that you suggested.  Since I'm new to this I'm not sure what the below tells me.  The section under Authority Section looks a little questionable but not sure what it should look like.
>
> Does this tell you anything of value?
>
> tsellers at bluto-laptop:~$ dig -x 192.168.1.1
>
> ; <<>> DiG 9.5.0-P2 <<>> -x 192.168.1.1
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62144
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;1.1.168.192.in-addr.arpa.	IN	PTR
>
> ;; AUTHORITY SECTION:
> 168.192.in-addr.arpa.	10800	IN	SOA	prisoner.iana.org. hostmaster.root-servers.org. 2002040800 1800 900 604800 604800
>
> ;; Query time: 486 msec
> ;; SERVER: 192.168.1.9#53(192.168.1.9)
> ;; WHEN: Fri May 15 23:36:23 2009
> ;; MSG SIZE  rcvd: 119
>
>
> --- On Fri, 5/15/09, Matthew Lechleider <matthew at lechleider.com> wrote:
>
>   
>> From: Matthew Lechleider <matthew at lechleider.com>
>> Subject: Re: [Cialug] DNS Reverse Lookup
>> To: "Central Iowa Linux Users Group" <cialug at cialug.org>
>> Date: Friday, May 15, 2009, 11:33 PM
>> Try dig with the flag -x for reverse
>> lookup.
>>
>> dig -x IP
>>
>>
>> Tom Sellers wrote:
>>     
>>> I have set up a DNS server on my home network and
>>>       
>> although it resolves machine names to IP addresses just fine
>> I can't seem to make it perform the reverse lookup
>> properly.
>>     
>>> Below is an example and the DIG information on my DNS
>>>       
>> server.
>>     
>>> Can anyone shed some light on where I have gone wrong
>>>       
>> here?
>>     
>>>       
>> ------------------------------------------------------------------------
>>     
>>> tsellers at bluto-laptop:~$ nslookup gw
>>> Server:       
>>>       
>> 192.168.1.9
>>     
>>> Address:    192.168.1.9#53
>>>
>>> Name:    gw.mydomain.com
>>> Address: 192.168.1.1
>>>
>>> tsellers at bluto-laptop:~$ nslookup 192.168.1.1
>>> Server:       
>>>       
>> 192.168.1.9
>>     
>>> Address:    192.168.1.9#53
>>>
>>> ** server can't find 1.1.168.192.in-addr.arpa.:
>>>       
>> NXDOMAIN
>>     
>>> tsellers at bluto-laptop:~$ dig mydomain.com
>>>
>>> ; <<>> DiG 9.5.0-P2 <<>>
>>>       
>> mydomain.com
>>     
>>> ;; global options:  printcmd
>>> ;; Got answer:
>>> ;; ->>HEADER<<- opcode: QUERY, status:
>>>       
>> NOERROR, id: 29703
>>     
>>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY:
>>>       
>> 1, ADDITIONAL: 0
>>     
>>> ;; QUESTION SECTION:
>>> ;mydomain.com.       
>>>       
>>     IN    A
>>     
>>> ;; AUTHORITY SECTION:
>>> mydomain.com.       
>>>       
>> 38400    IN   
>> SOA    bluto.mydomain.com.
>> admin.mydomain.com. 2007062001 28800 3600 604800 38400
>>     
>>> ;; Query time: 1 msec
>>> ;; SERVER: 192.168.1.9#53(192.168.1.9)
>>> ;; WHEN: Fri May 15 23:17:25 2009
>>> ;; MSG SIZE  rcvd: 78
>>>
>>>
>>>
>>>        
>>>
>>> _______________________________________________
>>> Cialug mailing list
>>> Cialug at cialug.org
>>> http://cialug.org/mailman/listinfo/cialug
>>>    
>>>       
>> _______________________________________________
>> Cialug mailing list
>> Cialug at cialug.org
>> http://cialug.org/mailman/listinfo/cialug
>>
>>     
>
>
>       
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>