Firstly you could tell us what *zone* you are having problems with.
While GoDaddy may not be telling you want you need you are not
telling us what we need to know to help you.
I don't blame GoDaddy for wanting to make sure that the delegation
is correct before you add DS record. DNSSEC can't fix
On 10/13/2013 17:34, John Oliver wrote:
Venting aside, does anyone have a contact at GoDaddy that doesn't suffer
from a terminal case of rectal-cranial invesrion? I'm mainly
experimenting with DNSSEC, and don't want to move all of my domains over
this one issue. But then, if this is the level o
I've been trying for three weeks to get GoDaddy to add a DS record for
one of my zones. Some of the excuses they've given as to why the fact
this hasn't happened is actually my fault:
"At this time, the issue is due to one or more nameservers associated
with the domain are not being configured co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/13/13 1:34 AM, Alan Clegg wrote:
>
> On Oct 12, 2013, at 7:59 PM, Alan Clegg wrote:
>
>>
>> On Oct 11, 2013, at 10:54 PM, David Newman
>> wrote:
>>
>>> 4. "Check that the new server is working and you can update the
>>> zone by using nsupda
On Oct 12 2013, John Levine wrote:
Please forgive my ignorance, and sorry about all the details. I have
not been able to find a detailed specification.
TXT records haven't changed since RFC 1034 and 1035.
You can have multiple strings per record, and multiple records per
name. At the applica
On Oct 12, 2013, at 7:59 PM, Alan Clegg wrote:
>
> On Oct 11, 2013, at 10:54 PM, David Newman wrote:
>
>> 4. "Check that the new server is working and you can update
>> the zone by using nsupdate."
>>
>> This is where things fall apart. I run 'rndc freeze' and increment the
>> zone file's se
6 matches
Mail list logo
