Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 32 subscribers
  • Views 11255 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

DNS Resolving

KoenT

Hello,

I've read the discussions about DNS-resolving but could you please help me out ?

Should it be possible to have internal DNS-names resolved in the reports ? Statement on the idea page is that it should work. I resolve against a Windows DNS-server with reverse lookup zones defined but the reports stay empty.  When I use the Test-button under 'Network - DNS' and enter an IP, the name is resolved correctly.

Should it be possible to have external DNS-names resolved in the reports ?

 

I'm well aware of the risks but it would be really handy to have a quick view on DNS-names while inspecting.

 

Thanks,

 

Koen



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Aditya Patel

    Hi, ,  and the development team. Are we able to get an update as to when this known issue NC-11142 will be resolved? I haven't seen it mentioned in the recent release of v17.1?

     

    Thanks,

    Erik

  • 0 in reply to RikS

    I have been trying to figure this out for a year now. Despite a bunch of discussion here and elsewhere, it is still unclear if this is a bug, missing feature, or as designed. I know that XG cannot function as a DNS server as of the current version I am running (17.0.8). External DNS resolution does not work right if you use the XG as the primary, so unless you have an internal DNS server, you must configure XG and DHCP scopes to use your ISP (or other DNS servers). This would lead me to believe that it is a bug or missing feature as cheap router/firewalls are at least capable of this basic "feature".

    I have been messing around with setting up a full featured internal DNS server using pfSense, but it didn't seem to make a difference even after pointing XG and DHCP to it for DNS. I think the crux of the problem is that the issue is actually a reverse DNS issue in that the XG would need to do RDNS lookups for the IP addresses in the reports. I don't know if it is possible to use the DNS Request Route Feature to point the XG to the internal DNS server via something like 1.0.168.192.in-addr.arpa, but I haven't gone that far in my testing yet. I am skeptical because the XG itself would need to be "told" to do RDNS lookups in these reports which I believe is the real problem. Therefore, at this point I am leaning to this actually being a mix between a bug/feature issue.

    Additional thoughts/brainstorming welcome....      

  • 0 in reply to bNaCl

    If you go the route of DNS routing it is highly recommended to do both forward and reverse zone to your internal server.

     

    Hope this helps

    -Ron