Koozali.org: home of the SME Server

Tinydns Clarification

Offline devtay

  • *
  • 145
  • +0/-0
Tinydns Clarification
« on: April 05, 2008, 09:08:08 PM »
Hello All,

I am having an issue with DNS. First, I have two SME Servers. One is the mail/web server (7.3) and the other is a proxy server (7.0). I am running dansguardian on the proxy server. I want to host a local development virtual domain on the mail/webserver. I created the virtual domain on the webserver. It works as long as I don't try to access it through the proxy. I have each of the browsers on the clients on the network configured to use the http://proxyserveraddress/proxy.pac file and the mail/webserver is the primary DNS with the proxy being the Secondary DNS. Since I could not access the local development site through the proxy, I disabled the pac file and tested it without having to go through the proxy to prove my issue.

In my proxy server, I changed the record for the http source to the local address of the mail/webserver. That seems to work as both servers are named mail.domain.com and proxy.domain.com respectively. So each one has the main domain named domain.com for the server. Using that logic, I went to the proxy server and made the local domain on it, then pointed the http to the local address of the mail/webserver. It won't work. I tried clearing the proxy cache, making an entry in the hosts file of the client and creating both domains on both servers and forwarding the address to remote for the proxy.

So, I read some more on the forums and what I read tells me I can not use replication between the two DNS servers in each SME server. What I think is happening is the proxy server becomes the main DNS source for the http request once the user logs in. Since this server is authoritative for the local domain, the primary domain setup in M$ Windoze is ignored. I tried clearing the proxy cache, making an entry in the hosts file of the client and creating both domains on both servers and forwarding the address to remote for the proxy. So, I just need some clarification that what I am trying to do won't work and some perspective as to why it works for the primary domain.

Thanks,
Devlin
You can't stop what's coming. It ain't all waiting on you.

Offline raem

  • *
  • 3,972
  • +4/-0
Re: Tinydns Clarification
« Reply #1 on: April 05, 2008, 11:25:17 PM »
devtay

If I understand you correctly (and I'm not sure that I do), you need to make only one server the master DNS server for your site.
In the Hostnames panel of that master server you need to add the second servers name & IP details.
In the second server run "Configure this server" and add in the first servers IP on the screen for where your DNS server is (this screen is usually left blank in most installs).
That way when you call up something on the second server, requests will go through the first server (as it is the master DNS serevr) and it then refers to one of the hostnames and forwards requests to the second server, Which is what as I interpret/assume you want to happen.

Perhaps you also (or instead of the above) need to use a proxypass db entry.

...

Offline devtay

  • *
  • 145
  • +0/-0
Re: Tinydns Clarification
« Reply #2 on: April 06, 2008, 05:18:04 AM »
Ray,

Thanks for the reply. It does indeed sound like you understand what I have done and am trying to do. I thought I had my "master" server properly configured by setting it up as my primary dns server on the clients. The main problem with my installation is that I was not there when it was completed. I think the best bet is to move the proxy over to the mail/webserver and shut down the second server as the mail/webserver can handle the load with no problem.

Anyways, I will take a look at the items you suggested on Monday when I get in. Your solution seems logical and is much better than the work around I am currently doing (put a html redirect in the secondary server's ibay). I am used to setting up replication partners with WINS and DNS and what you suggest sounds right along those lines. Thanks for the help.

Devlin
You can't stop what's coming. It ain't all waiting on you.