Koozali.org: home of the SME Server

Local DNS broken after 5.5 Upgrade

Paul Zagoridis

Local DNS broken after 5.5 Upgrade
« on: September 09, 2002, 07:44:14 AM »
I upgraded my SMEserver from 5.1.2 to 5.5. Everything seems to be working fine except local DNS. All client machines now get mail.zagz.com resolving to our external (firewall) IP address (150.101.196.166). This is the same result for all virtual hosts and virtual domains.

I'm running SMEserver as Server only inside a firewall with port forwarding. Before the upgrade SMEServer seemed to know local network went to local mail server 192.168.206.1 IP address.

I can't see anything in the FAQ or searching the phorum.

Maybe the fact that the DNS server field in Review configuration is blank? It used to show the SMEserver local address.

The server also provides DHCP leases with itself configured as the primary DNS. On the SME server config I have DNS and Gateway setup as the internal Firewal port (192.168.206.254) (net.host numbers changed).

Review configuration
Networking Parameters
Server Mode serveronly
Local IP address / subnet mask 192.168.206.1/255.255.255.0
Gateway 192.168.206.254
Additional local networks No additional networks defined
DHCP server enabled
Beginning of DHCP address range 192.168.206.101
End of DHCP address range 192.168.206.200
Server names
DNS server  
Web server wwwzagz.com
Proxy server proxy.zagz.com:3128
FTP server ftp.zagz.com
SMTP, POP, and IMAP mail servers mail.zagz.com
Domain information
Primary domain zagz.com
Virtual domains

Paul Zagoridis

FIXED Re: Local DNS broken after 5.5 Upgrade
« Reply #1 on: September 19, 2002, 12:33:23 PM »
OK I fixed it, so I thought I should update this thread in case anybody else is looking for the fix...

In the server console config I entered the ISP Primary DNS. The wording of the question says "You may need to specify an IP Address here if there is a firewall between this server and the internet". As this server is behind a firewall I entered it in there.

As a result SMEserver was entering using this DNS forwarder address.

The fix was to delete the entry for the Master DNS Server Address entry (leave it blank). SMEserver is now the master DNS for all its domains.

I don't know why this misconfig worked in 5.1.2 (actually reading the template I can see why but that's another story).