For someone to register a domain and listing our server name with a
bogus IP, the registry has to be incredibly careless
I wonder if he is seeing the same thing I was a few days ago. I had a
certain *.edu host listed as a nameserver of mine with several
registries (gandi for .com, arin for
On Jan 26 2009, Wolfgang S. Rupprecht wrote:
For someone to register a domain and listing our server name with a
bogus IP, the registry has to be incredibly careless
I wonder if he is seeing the same thing I was a few days ago. I had a
certain *.edu host listed as a nameserver of mine with
Right, but his question was regarding the host record for the name
server. You tell the registrar the name and IP address of the name
servers that are authoritative for the domain. The registrar then
pushes those glue records to the root servers. Root doesn't care what
the name and/or IP address
On 08-Jan-2009, at 03:41 , Dawn Connelly wrote:
Right, but his question was regarding the host record for the name
server. You tell the registrar the name and IP address of the name
servers that are authoritative for the domain. The registrar then
pushes those glue records to the root servers.
Milo Hyson wrote:
In our particular case, we have stale glue records for our name-
servers that appear to be coming from a domain we host that is owned
by someone else. Despite our best efforts, we have not been able to
reach the owners and thus have not been able to get the host records
changed
If different registrars contain different host records for the same
name server, what glue records are established in the root servers?
Suppose two domains at different registrars both list ns1.mydomain.com
as a nameserver but each gives a different IP. Are the results
undefined? Is there
6 matches
Mail list logo
