Matthew, I haven’t seen this problem in a long time where someone else submits data to cause the out-of-zone glue to appear. It’s possible there’s something happening at NETSOL that is causing this, but the best way is for you to go into your registrar and ensure they’re publishing the proper host records for your in-zone glue which should address this if nobody got back to you yet. It may also be easier to find someone on the dns-operations list than NANOG these days. - Jared
On Dec 15, 2020, at 11:43 AM, Matthew Crocker <matthew@corp.crocker.com> wrote:
I need to get Network Solutions to remove glue records for hosts in my domain. My domain isn’t registered with Network Solutions and they refuse to speak with me as I’m not a customer.
I’ve had my customer attempt to update their domain through Network Solutions but the only thing they can change is the NS record, not the underlying host glue record. I don’t think the glue records even need to exist as they are published by my domain already.
Does anyone have any contacts at Network Solutions that can help?
Example:
dig <MY_CUSTOMER>.com NS @i.gtld-servers.net.
; <<>> DiG 9.10.6 <<>> <MY_CUSTOMER>.com NS @i.gtld-servers.net. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24593 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3 ;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;<MY_CUSTOMER>.com. IN NS
;; AUTHORITY SECTION: <MY_CUSTOMER>.com. 172800 IN NS dns-auth4.crocker.com. <MY_CUSTOMER>.com. 172800 IN NS dns-auth3.crocker.com.
;; ADDITIONAL SECTION: dns-auth4.crocker.com. 172800 IN A 66.59.48.95 dns-auth3.crocker.com. 172800 IN A 66.59.48.94
;; Query time: 73 msec ;; SERVER: 192.43.172.30#53(192.43.172.30) ;; WHEN: Tue Dec 15 11:34:41 EST 2020 ;; MSG SIZE rcvd: 124
The correct servers are:
dns-auth3.crocker.com. 299 IN A 66.59.61.10 dns-auth4.crocker.com. 299 IN A 66.59.61.194