Hi
Sorry if I keep posting so many questions but...
how do I assign a domain name to the LAN set up on the Draytek? At present it seems to be set to Draytek.Vigor.
On my old router I could set the domain name but I cannot find where to set it in the web interface.
Also I am using the DHCP server but again, as clients are connecting, how can I get the router to automatically retrieve the hostname and map it to the assigned IP address so that I can use the full name to connect to different clients? (in the current instance, hostname is "helium", would like, from another machine, to use just helium or helium.Draytek.Vigor).

I don't really want to set up static addresses or host files if possible.

Regards
Ian

Draytek Vigor 2820n

OK

So I have tracked it down to the domain is called local.

Therefore if I use HOST-ID.local it works.

So where and how can I change the domain of the router from local to something else?

Hi there,

Did you ever figure this out? I too would like to know how to do this. Seems to be a glaring omission on the DHCP side of things.

I have 2930 router and the command in the FAQ "sys domainname <name>" fails asking to input wan1/wan2 so obviously not the right command.

Please anyone know how to set this? I have devices that require it.

Thanks.

Hi
I never found an answer. Also the ".local" domain no longer works.

I keep meaning to raise it with support. If I get a result I will post it.

The way of setting the domain name is via telnet command which is "sys domainname xxxxxx" where xxxx is yourname.

Except it now asks for a wan.
What I (we) want to do is set the DHCP server so that when it knows the hostname of a device on the local LAN, I can use this hostname to connect to another machine. I think the Domainname command is a red herring here for the requirement.
So far it seems that though most routers support this, the Draytek is not one of them.
The only way is to get the DHCP server to use the same ip for each machine and then use static hosts file on each machine ... Which kind of defeats the reason to use DHCP in he first place!