I have a strange observation on a new install that I can't explain.

I have a new Shuttle/AMD box running MDK 10.1 which seems to be running well. When I boot this machine, the DNS settings on my SMC router get messed up. I have to restart the router after the server is booted or nobody on the network can make any new connection. Took me a while to find the cause and effect but I cannot come up with a fix.

The server has a static IP address (192.168.2.112). All machines on the network use the router as the DNS server (192.168.2.1) I am not seeing any obvious differences in the network settings of other machines that are behaving correctly. The SMC router has the most recent software and I cannot see any setting or daemon that would have the Shuttle want to take control of that upon boot.

Does this make sense to anybody? Clearly I am not a network guru and randomly kick things until they work. I am running out of things to kick.

A booting machine should not be capable of changing settings on the router. Do you see the settings change through the router's control panel?

Do you have a DHCP or DNS server running on this PC?

I see no changes to the router configuration. Turning features (DHCP/ WIFI) on and off via control panel did not restore performance. My only fix has been to turn the router on/off.

I was turning off services/daemons that I did not think I needed to be loaded at boot time, and I did not see anything named DNS or DHCP.

I cannot SSH to the machine now, but tonight I will try to get a full list of what is running.

That gives me an idea. Is there a way to confirm each boot command at start up? Like type 'y' if you want the next task started. If I can slow down the boot process, maybe I can isolate exactly what task is making the router barf.

windows pc's send extra stuff to a DNS server. maby it is expecting it.