> On 01-Oct-2009, at 16:03, Scott Haneda wrote:
>> Is it also correct, I only need a NS glue record for the actual NS
>> itself. There does not need to be a glue record for very zone that I
>> am providing DNS for?
On 01.10.09 18:25, Matthew Pounsett wrote:
> The only case where glue *must* be
Yeah, I just ran a few queries and can't figure out what exactly it's
complaining about.
Matt
It's making a observation ("i" in a blue circle) that there were
not additional records for ns1.nacio.com being returned by
ns1.hostwizard.com presumable because ns1.hostwizard.com doesn't
serve the zo
In message <73e2882f-00b3-41cb-b46d-351774486...@conundrum.com>, Matthew Pounse
tt writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On 01-Oct-2009, at 19:03, Scott Haneda wrote:
>
> > So I see my NS is listed in the additional section. This to me
> > tells me there is in fact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-Oct-2009, at 19:03, Scott Haneda wrote:
So I see my NS is listed in the additional section. This to me
tells me there is in fact glue, so I should consider the report at http://intodns.com/hostwizard.com
to be inaccurate?
Yeah, I just r
On Oct 1, 2009, at 3:25 PM, Matthew Pounsett wrote:
On 01-Oct-2009, at 16:03, Scott Haneda wrote:
Is it also correct, I only need a NS glue record for the actual NS
itself. There does not need to be a glue record for very zone that
I am providing DNS for?
The only case where glue *must*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-Oct-2009, at 16:03, Scott Haneda wrote:
Is it also correct, I only need a NS glue record for the actual NS
itself. There does not need to be a glue record for very zone that
I am providing DNS for?
The only case where glue *must* be pre
Hello, I believe I understand what a glue record is, and why I would
need one. I would like some clarification if possible.
While I am not the hugest fan of the dns report services, this report
was brought to my attention:
http://www.intodns.com/hostwizard.com
It says I am missing glue for
7 matches
Mail list logo
