On 03/06/2015 02:51 PM, Andrew Sullivan wrote:
The problem is that you have host objects in the .com registry:
Server Name: A.NS.DOMADD.GETRESPONSE.COM
IP Address: 207.8.198.52
Registrar: NETWORK SOLUTIONS, LLC.
Whois Server: whois.networksolutions.com
Referral URL:http://networksolutions.com
I suspect you need to get netsol to remove those records. Anyway,
that's why there are records in the .com zone for those two names.
(There shouldn't be glue at all, because they're not in-baliwick, but
Verisign can't know that in advance so they just push all the in-zone
IP records that are registered with host objects out to the zone. I
don't really know any other way to do this at the scale of the .com
zone.) Why network solutions didn't remove those host objects when
they updated the nameservers for getresponse.com is something you'll
need to ask them.
Hi,
Thank you I've contacted NETSOL to remove that entries but this name
servers (A.NS.DOMADD.GETRESPONSE.COM, B.NS.DOMADD.GETRESPONSE.COM) was
never used in domain getresponse.com (and any other domain). Do you know
why such registry of namservers are used why .COM operator. If Verisign
want to add record blindly they should ask DNS instead a DB which have
strange entries :(
P.S. I agree that automatic glue records in .COM is pretty bad idea.
Moving name servers is very very painful :(
Thank you,
--
Greg
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-jobs mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
