Forum Discussion

Nicolas_DE_2299's avatar
Nicolas_DE_2299
Icon for Nimbostratus rankNimbostratus
Jan 21, 2016
Solved

Issue to resolv local DNS name on APM (without domain extension)

Hi all,

 

My issue concern DNS resolution for some HTTP internal servers.

 

For example, we have an intranet accessible on url "", if i configure a portal access ressource, this one is unnaccessible (firefox return DNS resolution problem). If i put resolution is working, but our web site return an error (web server accept only host "intranet", not "intranet.mutu.local").

 

I have same issue for many our web-sites, and put the domain extension is not the solution.

 

From graphical interface of F5, i configure host resolution for 'intranet', but it doesn't work.

 

Is there a solution to my probem? Thanks in advance.

 

  • Portal Access doesn't support BIG-IP's static host resolution feature (this is F5 enhancement request ID 223060). However, it does support the normal system resolver and its settings. You should simply have to set up the "search domain" in System => Configuration => DNS.

     

5 Replies

  • Lucas_Thompson_'s avatar
    Lucas_Thompson_
    Historic F5 Account

    Portal Access doesn't support BIG-IP's static host resolution feature (this is F5 enhancement request ID 223060). However, it does support the normal system resolver and its settings. You should simply have to set up the "search domain" in System => Configuration => DNS.

     

  • Result is the same if i configure domain "mutu.local" in "DNS search domain List" field. Is there another action to do to activate this functionnality?

     

    Thanks for your help.

     

  • Hi Laconi,

     

    You will need to point the BigIP to a DNS server that can resolve the names needed for the portal access. Did you do this or just add the search domain list?

     

    -Seth

     

  • Hi Seth,

     

    In the same DNS configuration page (System->Configuration->Device->DNS), i configured our DNS internal server in "DNS Lookup Server List" also. I didn't do anything else, is-it sufficient?

     

    My DNS server is able to resolv the dns name "intranet" of course.

     

  • Hi Laconi,

    the solution is described on Ask F5 AskF5 SOL39744305.

    Its about the
    ndots
    Parameter in the
    /etc/resolv.conf
    .

    Problem is fixed in v12.1.

    Cheers, Stephan