Am 05.12.2014 um 19:25 schrieb Robert Moskowitz:
On 12/05/2014 11:53 AM, li...@rhsoft.net wrote:
Am 05.12.2014 um 17:35 schrieb Robert Moskowitz:
On 12/05/2014 11:24 AM, li...@rhsoft.net wrote:
it's *your* responsibility to look at your own public whois and verify
your configurations published to the world and *not* the registrars
Domain servers in listed order:
Z9M9Z.HTT-CONSULT.COM
ONLO.HTT-CONSULT.COM
NS2.CLEARRATE.COM
NS1.ICSL.NET
NS1.CLEARRATE.COM
Yep, it is. And I know I looked at this when I moved registrars. I
have deleted the glue record as well. Now to figure out how to get glue
records for NS servers in other domains. The Registrar's tool only
allows creating glue records within your own domain. Take this question
over the the DNS list
no, you just have to read what a GLUE record is
And these wonderful DNS web tools that report no glue records for NS
servers not under my domain
you just need to read *and* understand the output
not offending; a fool with a tool is still a fool :-)
* there is an "informational" icon
* the text starts with INFO
* the text contains "This is ok"
* but you should know that in this case an extra A record lookup
is required in order to get the IPs of your NS records
the last point is pretty clear and just a explaination
* a NS in your own GLUE needs one lookup less
* a "dig NS htt-consult.com @ns2.clearrate.com" needs one more
* this don't matter as long "clearrate.com" itself has no problems
____________________________________________
INFO: GLUE was not sent when I asked your nameservers for your NS
records.This is ok but you should know that in this case an extra A
record lookup is required in order to get the IPs of your NS records.
The nameservers without glue are:
