DHCP-assigned domain name and nameservers not taken over if TCP/IP Attribute 5 contains invalid value

In an Extended COnfig scenario, if the remanent data is deleted and te host application does not set TCP/IP attribute 5 during the startup, so that the value remains at IP and/or netmask zero, then the first assignment of a domainname and/or nameservers via DHCP is not stored in the attribute value nor in the remament data. The assigned IP config itself will be stored nevertheless.

The reason for this is the default value zero for IP address/netmask in the TCP/IP object which itself is invalid (fails in Tcp_CheckInterfaceConfig), so if this is augmented with a domanname or nameservers in the DHCP option callback, it is still invalid and the set is silently rejected).