1

What are the arguments against running an authoritive nameserver (primary) e.g. bind in a ipv6 only environment? In the current setup the machine dedicated to the nameserver has only direct ipv6 connectivity (ipv4 only via NAT) - the secondary ns would be dualstack (the one from the hosting provider)

Improve this question

1 Answer 1

Reset to default
2

Strictly speaking there is nothing wrong with that configuration. In practice there are many poorly written resolver stacks in use in various applications.

You will notice that Hurricane Electric does not dual-stack ns1.he.net (ns1 is IPv4 only, ns2 through ns5 are fully dual-stacked). That is arguably an overly cautious approach.

I would not choose an IPv6-only host as a primary authoritative nameserver. However, I would feel comfortable having a dual-stacked primary and IPv6-only secondary (or tertiary, etc).

Improve this answer
2
  • Do you also have a remark about the "IPv4 via NAT" alternative? In general I don't like NAT, but if it would be the only viable solution I would have to accept that.
    – mschenk74
    Feb 24, 2014 at 10:28
  • Since ipv4 is needed for the zone tranfer to the secondary, etc. nameservers according to my provider of those additional servers I can forget this alternative now.
    – mschenk74
    Mar 11, 2014 at 14:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .