Lots of protocol clients reguire server address, but MT insists that IP addresses should be used. If one types in mnemonic address it is immediately resolved to IP and IP is set.
It is very common that IP address changes so mnemonic address is the only useful address to be used. MT does not allow that. It should.
I noticed this in the NTP client. I’d like to use pool.ntp.org but I’m forced to choose one IP address instead.
the problem would be that the DNS name would have to be resolved. people with thousands of rules will get into trouble when all 1000 DNS names will have to be resolved every second. currently you can make a script that resolves a DNS name and updates your rule. this is fine for a small number of rules or places where you need this
he’s not talking about firewall rules, but for all other clients. I would LOVE to see this.
ntp client
l2tp-client
pptp-client
etc …
it doesn’t matter, same still applies. how often would the DNS names have to be resolved, what would happen if it fails, what would happen if the DNS names would be too many etc?
ntp client only would resolve it once every few minutes or hours, depending on drift.
ppp-clients would only resolve it when they go to make the outbound connection. sometimes this is weeks or months at a time. Only resolve it when making the initial connection, not during an established one.
PS - Windows dialup networking (VPN) does this without problems : ) Not that I like windows, just trying to give an example.
Sam
Also we have dns cache, am I right?
sounds good, but most requests from users have been about rules and address lists. we’ll see what we can do