Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 3 subscribers
  • Views 950 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[7.403]Reverse-dns doesn't work

wingman
I am unable to use nslookup. It seems that reverse dns doesn't work at all. I've searched both the kb and old threads and I think I need to define something on the request routing tab. I have no issue "talking" to the devices within the network. 
I don't have an internal DNS server.(reverse-dns issue is not related to the current firmware version)
Could you please advice on how to proceed?


This thread was automatically locked due to age.
Parents
  • 0
    (Oops - I just noticed the following doesn't apply because you don't have an internal DNS server.)

    BarryG recently taught many of us this trick.  You're right that it goes in 'Request Routing'.

    So, for example, if your internal network is 172.16.1.0/24, define:

    1.16.172.in-addr.arpa → 


    Cheers - Bob
    PS I don't know how to do reverse DNS with the Astaro DNS Proxy.

  • 0 in reply to BAlfson
    Indeed I don;t have an internal dns

    When trying to use nslookup
    server: Unknown
    address: 192.168.2.100 (astaro address)

    and I am unable to resolve any client

    I've also tried adding static entries for the client

    i.e  client A--> 172.16.1.2 with no luck [:(]
Reply
  • 0 in reply to BAlfson
    Indeed I don;t have an internal dns

    When trying to use nslookup
    server: Unknown
    address: 192.168.2.100 (astaro address)

    and I am unable to resolve any client

    I've also tried adding static entries for the client

    i.e  client A--> 172.16.1.2 with no luck [:(]
Children