DNS Error

[Hoof Hearted]

SBS2008 + 15 Cients + Router on a single network.

My clients cannot access the Internet when I configure them to use the Wingate Proxy Server. They get a Wingate page returned which says: Host not found. Name lookup for mywebpage.com failed.

When I check the Wingate Configuration I noticed in System -> DNS Service -> Bindings, there is software Loopback Interface and the Physical Adapter listed. They are both configured to Port 53 and the status is 'error'.

I checked the log files and found this.

12/09/09 09:38:50 Error: Service failed startup on interface 127.0.0.1:53 error 10013
12/09/09 09:38:50 Error: Service failed startup on interface 192.168.16.2:53 error 10013

What might the problem be?

Ian

[adrien]

looks like there is something else running on port 53 preventing the WinGate DNS service from starting on that port.

Are you running the MS DNS Server also on that machine?

[Hoof Hearted]

Yes I am running the MS DNS Server, it is automatically installed as part of SBS 2008. I tried disabling the Wingate DNS, but my clients still couldn't get internet access. So I re-enabled it. What is the correct course of action?

This makes me want to ask another question.... In the Wingate System Tab, I can see things like Pop2, SMTP, Imap, Email..... My only reason for installing Wingate is so that the company can monitor the web pages that the employees are visiting. Nothing else is of interest. Should I disable those other services?

Ian

[logan]

On a server running MS DNS, the DNS settings of the network adapters will point to localhost. WinGate ignores localhost DNS servers, so may not have any DNS servers available to use. You can manually configure WinGate to use one of your ISP DNS servers for name resolution in GateKeeper -> System -> DNS/WINS Resolver -> DNS.

You can disable/delete unneeded services if you do not intend to use them. They can always be reenabled or reinstalled later should you change your mind.

[Hoof Hearted]

I manually configured my ISP's DNS server addresses now, but I still have the original error on both of my DNS Service bindings. I think maybe I need to solve the problem that both DNS Services are attempting to use port 53. What is the accepted workaround for this?

[adrien]

normally,

a) disable WinGate DNS Server. Client machines will then use MS DNS Server
b) set a forwarded in the MS DNS Server to forward requests to your ISP DNS Server
c) in your LAN adapter on the WinGate machine, set the DNS server to 127.0.0.1 (it might be that already)
d) in your WinGate DNS resolver settings, manually add the IP of your LAN adapter (of the WinGate machine) so WinGAte can do lookups to the MS DNS server... or you could enter your ISP DNS Server IP in there instead or as well.

Adrien

[Hoof Hearted]

Ok thank you, that all made sense. The DNS on the Lan Adapter is set to 192.168.16.2 (It's own Lan Address). I assume that is ok. I put the ISP and Lan Adapter addresses in the DNS resolver settings.

It's evening here . So I'm doing this from home via Terminal Services. So I only have access to the server. When I try to open a web page now, I'm getting the follwing error:

Socket Error 10049 {Thd 10732} [socket #DE0, 192.168.16.2:9891 to :0]

Is this an easy fix?

Ian

[adrien]

that means WinGate failed to look up the IP.

Did you do step (d)? Maybe best to go with the ISP DNS server there.

[Hoof Hearted]

Hmmm... I had put the ISP DNS in there as well as the Lan Adapter, but the Lan adapter was at the top priority. So I took it out and now my clients can get web access via Wingate.

Thanks for all your help.

Ian

[Alen]

The DNS on the Lan Adapter is set to 192.168.16.2 (It's own Lan Address). I assume that is ok. I put the ISP and Lan Adapter addresses in the DNS resolver settings.

AFAIK, MS recommends setting local loop address rather than LAN ip on MS OS based DNS servers (this is 100% correct for AD integrated DNS servers).