Hi,
Apologies if this has come up before but I could not find anything on this through searching. There seems to be a bug with the DNS Manager in that it does not accept LAN IPs (eg. Class A address like 10.x.x.x or class C like 192.168.x.x).
We setup a server in house for testing / dev purposes.
After creating the default DNS records, which created the usual @, mail, ns1 and ns2 records with the Public IPs, if we attempted to change the existing records or create new records with LAN IPs, Sentora comes back with :-
ERROR DNS NOT SAVED
IP Address is not a valid IPV4 address.
Even if we tried with the example provided by Sentora (192.168.1.1) shown on the DNS Manager page :-
The A record contains an IPv4 address. Its target is an IPv4 address, e.g. '192.168.1.1'.
it still comes back with the same error that it is not a valid IPV4 address.
As this is an internal only server, we want it to recognise / resolve to local IP addresses.
Is there a trick to this or is this a bug ?
Thanks.
CK
Apologies if this has come up before but I could not find anything on this through searching. There seems to be a bug with the DNS Manager in that it does not accept LAN IPs (eg. Class A address like 10.x.x.x or class C like 192.168.x.x).
We setup a server in house for testing / dev purposes.
After creating the default DNS records, which created the usual @, mail, ns1 and ns2 records with the Public IPs, if we attempted to change the existing records or create new records with LAN IPs, Sentora comes back with :-
ERROR DNS NOT SAVED
IP Address is not a valid IPV4 address.
Even if we tried with the example provided by Sentora (192.168.1.1) shown on the DNS Manager page :-
The A record contains an IPv4 address. Its target is an IPv4 address, e.g. '192.168.1.1'.
it still comes back with the same error that it is not a valid IPV4 address.
As this is an internal only server, we want it to recognise / resolve to local IP addresses.
Is there a trick to this or is this a bug ?
Thanks.
CK
