On Mon, January 11, 2010 9:10 pm, Matthew Pounsett wrote:
> I suspect that, even though they threw an error, your registrar went ahead
> and passed on the same IPv4 address for both name servers to the registry.
I think this may have been the problem...
I went back in to the registrar's DNS cont
On Mon, January 11, 2010 8:33 pm, Matthew Pounsett wrote:
> The problem may be at Kloth.. but at least one of the many possible
> problems they might be having could be corrected by a slightly different
> configuration at your end.
Thanks Matt for your (and others) continued help with this - it i
On Mon, January 11, 2010 6:27 pm, Miles Mccredie wrote:
> FWIW, this is what I'm seeing from an IPv4 only host. Not sure if the
> unexpected source is the problem that kloth.net is seeing or whether
> it's the result of putting
>> *;; reply from unexpected source: 77.103.161.36#60741, expected
>
On Mon, January 11, 2010 5:57 pm, Rick Dicaire wrote:
> While this is not in response to your original question, I am curious.
> I'm not sure if you were part of the discussion we just had on IRC
> freenode #ipv6, but querying a .org TLD NS for records for ns1
> and ns2.v6ns.org return no a
I would be grateful if someone might be able to shed some light on an
apparent problem I've got with an experimental DNS I have setup.
Specifically, the Dig tool at http://www.kloth.net/services/dig.php seems
unable to resolve my records and I can't help but feel it's a problem at
my end rather th
5 matches
Mail list logo
