The fritz.box, which you are using for VOIP has no option to set VLAN. DNS knows only IP no VLAN, so you use the IP. If your domain is only internal then I suggest that you use .local instead of .de because .de is kept in the DNS on the Internet.
Yes, that´s true!
The idea is, to assign an utagged port of the Mikrotik for the Fritzbox. The Box will receive an IP from this vlan, if the Box runs in IP-Client Mode. All the local Fritzbox Ports (WLAN included) will host the vlan and I can connect the IP Phones to this Subnet. I hope this will work!
What exactly do you mean with this:
VLAN is separating the networks and subnets also do that as long you do not enable routing/GW between them.
My intention is, to make the LAN much more secure in order to move specific clients in a separate vlan. E.g., it does not make sense to have SmartHome devices in the same subnet together with Xbox, PlayStation and Co.
For some other clients,I think, it also makes sense, to spend them an own vlan (Sonos Multiroom-Device) but the players should have access to the internet and to the NAS in another vlan. The players should also communicate with the controllers which are also located in annother vlan. This is just an idea and if this will work, I don´t know.
Today I tried the following:
- entering a static entry to the DNS-Server with the new FQDN. This works fine
- installing the script into the "DHCP-Lease-Script Window" of the specific dhcp-Server. As soon as the Client will get the lease, the DNS-Entry is processed and I can ping the client with FQDN. As soon as lease expires (or is deleted) the Static entry in the DNS-Server will be removed. If I am right, I have to install the script for each dhcp-server.