Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: visionoz on September 22, 2007, 09:59:11 PM
-
Hi,
I wonder if anyone else has tried this and found that the SME7.2 server thereafter does not resolve domain names?
- I used a Win2K3 as the DC in a LAN environment with it functioning also as a DHCP/DNS server, and Active Directory set up correctly - therefore I turned off the DHCP service portion of SME server (which was used in the dedicated server/gateway mode) and put in the Win2K3 server's IP in the "Corporate DNS Server Address" section of the configuration process.
Now that the LAN environment has changed and a DC is no longer required, I re-configured the SME server by removing the IP of the Win2K3 server, turned on DHCP but now though the SME server is working fine in all respects, it does not any longer allow any LAN users connected to it to obtain DNS resolution at all, pinging to external domains by IPs work from the SME server though.
Only by re-instating the DC back into the LAN environment then will the DNS resolution work!! Looks like the the removal of the Corporate DNS Server's IP address does not get updated at all.
If anyone has already come across such an issue and know the solution to it, I would greatly appreciate some referral advice as to how to put the SME server back to the original intended functionality.
Thanks & regards
-
Suggestions:
- Check the setting for DNS for the Primary Domain - it should be 'Resolve locally'. (Removing the IP addresses from the 'corporate DNS settings' page may not re-configure the domain DNS settings...)
- Is there a firewall between the SME and the Internet that may be blocking outbound DNS queries?
- Try 'Reconfigure' then 'Reboot' from Administration::Reboot or shutdown
-
Only by re-instating the DC back into the LAN environment then will the DNS resolution work!! Looks like the the removal of the Corporate DNS Server's IP address does not get updated at all.
If you suspect this is the case please report bugs and potential bugs in the bug tracker, along with evidence. Thanks.
-
If you suspect this is the case please report bugs and potential bugs in the bug tracker, along with evidence. Thanks.
I noticed this myself yesterday. Bug filed here: http://bugs.contribs.org/show_bug.cgi?id=3415
For now, to remove the corporate DNS setting do this:
config delprop dnscache Forwarder
signal-event dns-update
-
I noticed this myself yesterday. Bug filed here: http://bugs.contribs.org/show_bug.cgi?id=3415
Thanks Paul, didn't see this bug.
*edit, scrap that - seen email :lol:
-
Thanks Paul, didn't see this bug.
That's because my timing is impeccable :-) I just filed it 2 minutes before posting.
-
Ahhh!! Thanks byte for pointing out that it might be a bug (I shall post such things that I suspect to be so in the bug tracker in future) and pfloor for also noticing the problem I had - I did check all the settings as you did but did not really try to find out in the manual for the commands to perform the db prop changes but at aro 2-3am in the morning I think I can be forgiven!! Will try the suggested solution
Thanks all
-
I somehow got caught on that one.
Had 3 or 4 goes at removing it and restarting it, then found if I used server-manager it stayed deleted first go.