cancel
Showing results for 
Search instead for 
Did you mean: 
KPeter
Level 7

webGW7: short DNS vs FQDN problem (DNS suffix)

Jump to solution

Hello!

Could you please help me what to configure in order to use short DNS names instead of FQDN? Is it possible?

The problem is, that we would like to access an internal server with its short name, and get from the webgw proxy the error of "The host is not resolvable". This is when using Firefox, using IE throws a 404 error.

If we try to access "server1", the proxy throws the error abowe. If we try to access the same server with FQDN (server1.test.local), everything is OK.

I tried to troubleshoot this at the webGW GUI (Troubleshooting -> Network Tools -> nslookup), and got this:

;; Got SERVFAIL reply from 10.0.1.11, trying next server

;; Got SERVFAIL reply from 10.0.1.12, trying next server

Server:                 10.0.1.13

Address:             10.0.1.13#53

** server can't find server1: SERVFAIL

So DNS is not working on the proxy if using short names. If using FQDN, everything is OK. At the clients the DNS suffix is set, it is coming from the DHCP server. It seems that browsers dont change the URL, and send it without any change to the proxy, and the proxy can handle short names. The webGW proxy is joined to the domain, but does not append the domain name to the end of the short URL.

Is it possible somehow to give DNS suffix(es) to webGW?  Or how should this problem be solved?

TIA,

     Peter

Message was edited by: KPeter on 1/26/11 9:36:38 AM CST
0 Kudos
1 Solution

Accepted Solutions
eelsasser
Level 15

Re: webGW7: short DNS vs FQDN problem (DNS suffix)

Jump to solution

Do you have your /etc/resolv.conf configured with a search suffix?

### BEGIN AUTOGENERATED CONFIG
### END AUTOGENERATED CONFIG
search mydomain.local mydomain.com sub.mydomain.local

This should append the domain to the host name. I think it was introduced to do so in version 7.0.1.5 and higher.

Also, as a general rule, you normally shouldn't proxy internal hosts through a gateway. Exclusions for internal hosts and IP ranges are usually applied in the browser so you don't proxy internal traffic. There are, of course, reasons people want to do this, but it is uncommon.

Message was edited by: Erik Elsasser on 1/26/11 10:05:28 AM CST
0 Kudos
2 Replies
eelsasser
Level 15

Re: webGW7: short DNS vs FQDN problem (DNS suffix)

Jump to solution

Do you have your /etc/resolv.conf configured with a search suffix?

### BEGIN AUTOGENERATED CONFIG
### END AUTOGENERATED CONFIG
search mydomain.local mydomain.com sub.mydomain.local

This should append the domain to the host name. I think it was introduced to do so in version 7.0.1.5 and higher.

Also, as a general rule, you normally shouldn't proxy internal hosts through a gateway. Exclusions for internal hosts and IP ranges are usually applied in the browser so you don't proxy internal traffic. There are, of course, reasons people want to do this, but it is uncommon.

Message was edited by: Erik Elsasser on 1/26/11 10:05:28 AM CST
0 Kudos
KPeter
Level 7

Re: webGW7: short DNS vs FQDN problem (DNS suffix)

Jump to solution

Dear Erik,

Thanks for your answer, that was what I was looking for. This solved the problem.

BR,

     Peter

0 Kudos