Topic: DNS under SME-Server 5.5

[Paul Zagoridis]

I upgraded my SMEserver from 5.1.2 to 5.5 and local network name resolution has broken. It is setup as Server only, a firewall is forwarding ports to the SME box which hosts mail and web services only.

All local network hosts get sent to the external IP address now. Obviously this doesn't work.

Looking at named.conf all the virtual domains are set to forward like this...

zone "206.168.192.in-addr.arpa."
{
        type forward;
        forward first;

        forwarders { 192.168.206.254; };

};

zone "zagz.com"
{
    type forward;
        forward first;

        forwarders { 192.168.206.254; };

};

Now I'm sure that's not right. Shouldn't the SMEserver be the master for all virtual domains? i.e. type master; there are zone files for every virtual zone (db.zagz.com)

DNS queries not resolved locally should pass to the firewall (192.168.206.254) which is set up as the primary DNS for the SME server.

Am I missing something in the logic?

If I'm right how do I change the behaviour without custom templates? This all used to work before the upgrade.

Thanks in advance for your help

[Paul Zagoridis]

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).

[mbru]

Thank you for posting your fix to this problem.  I had similar DNS issues and, as you suggested, went into the SME configuration and deleted the  DNS address I had previously entered (my ISP's Primary DNS address).   That seems to have fixed my problem.  Thanks again.

[Paul Zagoridis]

Glad it helped. I like it when people post the fix even when they work it out themselves. It was my way of giving back to the community.

Regards

Paul