On 11/05/2012 11:24 PM, Rob Crittenden wrote:
Martin Kosek wrote:
On 11/02/2012 04:35 PM, Rob Crittenden wrote:
Martin Kosek wrote:
On 10/25/2012 04:01 PM, Martin Kosek wrote:
Nameserver hostname passed to dnszone_add command was always treated
as FQDN even though it was a relative DNS name
Martin Kosek wrote:
On 11/02/2012 04:35 PM, Rob Crittenden wrote:
Martin Kosek wrote:
On 10/25/2012 04:01 PM, Martin Kosek wrote:
Nameserver hostname passed to dnszone_add command was always treated
as FQDN even though it was a relative DNS name to the new zone. All
relative names were being
Martin Kosek wrote:
On 10/25/2012 04:01 PM, Martin Kosek wrote:
Nameserver hostname passed to dnszone_add command was always treated
as FQDN even though it was a relative DNS name to the new zone. All
relative names were being rejected as unresolvable.
Modify --name-server option processing in
On 11/02/2012 04:35 PM, Rob Crittenden wrote:
Martin Kosek wrote:
On 10/25/2012 04:01 PM, Martin Kosek wrote:
Nameserver hostname passed to dnszone_add command was always treated
as FQDN even though it was a relative DNS name to the new zone. All
relative names were being rejected as
Hello,
please see my comment in the patch below.
On 10/25/2012 04:04 PM, Martin Kosek wrote:
On 10/25/2012 04:01 PM, Martin Kosek wrote:
Nameserver hostname passed to dnszone_add command was always treated
as FQDN even though it was a relative DNS name to the new zone. All
relative names were
On 10/25/2012 04:01 PM, Martin Kosek wrote:
Nameserver hostname passed to dnszone_add command was always treated
as FQDN even though it was a relative DNS name to the new zone. All
relative names were being rejected as unresolvable.
Modify --name-server option processing in dnszone_add and
