Re: Freeze/thaw and signed zone files

On 23/02/2019 05:28, @lbutlr wrote: > I did try manually updating vi nsupdate -l > >> zone example.com >> update add example.com. 86400 IN SOA ns1.example.net. >> admin.example.com. 2019022200 3600 300 1209600 3600 >> update add konamicode.example.com. 86400 IN CNAME www.example.com

Re: Freeze/thaw and signed zone files

On 23 Feb 2019, at 14:45, Mark Andrews wrote: > On IPv6 why wouldn’t you support it? Our ISP does not support it. We get 5 static IPv4 addresses and no IPv6 at all. -- Critics look at actresses one of two ways: you're either bankable or boinkable.

Re: Freeze/thaw and signed zone files

On IPv6 why wouldn’t you support it? The world ran out of IPv4 addresses years ago and IPv4 is only limping along now due to ISPs spending big money to put in CGN boxes which you are paying for. Turning on IPv6 reduces the required size of these CGN boxes with on average 70% of residential

Re: Freeze/thaw and signed zone files

On 22 Feb 2019, at 12:28, @lbutlr wrote: > ; Communication with ::1#53 failed: timed out I am still getting this error whenever I try to make a change in the zone with nsupdate -l, should I not worry about it? I mean, the records appear to be updating… 路‍♀️ -- First we must assume a