CIRA caching ancient glue records.
I'm having a strange issue (for a couple years) in that when my NS server change IPs (once every 2-3 years as I change ISPs) CIRA doesn't change it's glue records accordingly. For instance... I move my NS servers ns1 and ns2 and of course their IPs change.. ns1.domain.ca 172.16.101.1 ns2.domain.ca 172.16.101.2 I will log into my registrar and try and have them update the zone (the two registrars I use have different behaviour). After a day or so I can see the whois info changes yet the OLD IPs for ns1 and ns2 persist. To get around this I have to come up with 'new' names for the DNS servers... I've so far used up: ns1,ns2.$domain a.ns,b.ns.$domain dnsa,dnsb.$domain nsa,nsb.$domain Does anyone have any suggestion on how I can ask cira to just flush all glue records so I can go back to my preferred NS names? Taking out this root domain nerfs about a dozen other domains. I'm about to just start chosing random strings for the NS server names but it is a bit much to ask folks to update their NS to joiafjsdpfoij.$domain.com. :P This behaviour persists across multiple .ca registrars which leads me to believe something at CIRA is not being reset properly (ie. when registrar does a zone update they are not requesting a flush or something...). I suppose I _could_ try moving my root domain to another registrar but again that will take me offline yet again and induce another bout of DNS rage. -- Sean P.S. Support at either canreg or domainsatcost has not been _any_ help so far.
I would, of course, suggest using EasyDNS for a variety of reasons, rather than running your own authoritative nameservers, but you of all people may have valid reasons to run your own :-). I also enjoy using EasyDNS because their support staff are responsive, and, ultimately, if you need to, you can reach the president (Mark Jeftovic) directly through any number of channels. Also, they're in Canada and therefore subject to Canadian law. None of which really helps you at the moment. Yes, it sounds like something's broken at CIRA - good luck figuring it out. -Adam Thompson athompso@athompso.net (204) 291-7950 - direct (204) 489-6515 - fax
-----Original Message----- From: roundtable-bounces@muug.mb.ca [mailto:roundtable- bounces@muug.mb.ca] On Behalf Of Sean Cody Sent: Sunday, April 01, 2012 12:53 PM To: Continuation of Round Table discussion Subject: [RndTbl] CIRA caching ancient glue records.
I'm having a strange issue (for a couple years) in that when my NS server change IPs (once every 2-3 years as I change ISPs) CIRA doesn't change it's glue records accordingly.
For instance... I move my NS servers ns1 and ns2 and of course their IPs change.. ns1.domain.ca 172.16.101.1 ns2.domain.ca 172.16.101.2
I will log into my registrar and try and have them update the zone (the two registrars I use have different behaviour).
After a day or so I can see the whois info changes yet the OLD IPs for ns1 and ns2 persist.
To get around this I have to come up with 'new' names for the DNS servers...
I've so far used up: ns1,ns2.$domain a.ns,b.ns.$domain dnsa,dnsb.$domain nsa,nsb.$domain
Does anyone have any suggestion on how I can ask cira to just flush all glue records so I can go back to my preferred NS names? Taking out this root domain nerfs about a dozen other domains.
I'm about to just start chosing random strings for the NS server names but it is a bit much to ask folks to update their NS to joiafjsdpfoij.$domain.com. :P
This behaviour persists across multiple .ca registrars which leads me to believe something at CIRA is not being reset properly (ie. when registrar does a zone update they are not requesting a flush or something...).
I suppose I _could_ try moving my root domain to another registrar but again that will take me offline yet again and induce another bout of DNS rage.
-- Sean P.S. Support at either canreg or domainsatcost has not been _any_ help so far. _______________________________________________ Roundtable mailing list Roundtable@muug.mb.ca http://www.muug.mb.ca/mailman/listinfo/roundtable
I think you raised this issue before. Have you contacted customer service at CIRA? I would think this would be a relatively common occurence. On 01/04/12 12:53, Sean Cody wrote:
I'm having a strange issue (for a couple years) in that when my NS server change IPs (once every 2-3 years as I change ISPs) CIRA doesn't change it's glue records accordingly.
For instance... I move my NS servers ns1 and ns2 and of course their IPs change.. ns1.domain.ca 172.16.101.1 ns2.domain.ca 172.16.101.2
I will log into my registrar and try and have them update the zone (the two registrars I use have different behaviour).
After a day or so I can see the whois info changes yet the OLD IPs for ns1 and ns2 persist.
To get around this I have to come up with 'new' names for the DNS servers...
I've so far used up: ns1,ns2.$domain a.ns,b.ns.$domain dnsa,dnsb.$domain nsa,nsb.$domain
Does anyone have any suggestion on how I can ask cira to just flush all glue records so I can go back to my preferred NS names? Taking out this root domain nerfs about a dozen other domains.
I'm about to just start chosing random strings for the NS server names but it is a bit much to ask folks to update their NS to joiafjsdpfoij.$domain.com. :P
This behaviour persists across multiple .ca registrars which leads me to believe something at CIRA is not being reset properly (ie. when registrar does a zone update they are not requesting a flush or something...).
I suppose I _could_ try moving my root domain to another registrar but again that will take me offline yet again and induce another bout of DNS rage.
Last time I tried, I was immediately dumped to the registrar. A very sour experience. Will try again. -- Sean On 2012-04-01, at 5:29 PM, Bill Reid <billreid@shaw.ca> wrote:
I think you raised this issue before. Have you contacted customer service at CIRA? I would think this would be a relatively common occurence.
On 01/04/12 12:53, Sean Cody wrote:
I'm having a strange issue (for a couple years) in that when my NS server change IPs (once every 2-3 years as I change ISPs) CIRA doesn't change it's glue records accordingly.
For instance... I move my NS servers ns1 and ns2 and of course their IPs change.. ns1.domain.ca 172.16.101.1 ns2.domain.ca 172.16.101.2
I will log into my registrar and try and have them update the zone (the two registrars I use have different behaviour).
After a day or so I can see the whois info changes yet the OLD IPs for ns1 and ns2 persist.
To get around this I have to come up with 'new' names for the DNS servers...
I've so far used up: ns1,ns2.$domain a.ns,b.ns.$domain dnsa,dnsb.$domain nsa,nsb.$domain
Does anyone have any suggestion on how I can ask cira to just flush all glue records so I can go back to my preferred NS names? Taking out this root domain nerfs about a dozen other domains.
I'm about to just start chosing random strings for the NS server names but it is a bit much to ask folks to update their NS to joiafjsdpfoij.$domain.com. :P
This behaviour persists across multiple .ca registrars which leads me to believe something at CIRA is not being reset properly (ie. when registrar does a zone update they are not requesting a flush or something...).
I suppose I _could_ try moving my root domain to another registrar but again that will take me offline yet again and induce another bout of DNS rage.
_______________________________________________ Roundtable mailing list Roundtable@muug.mb.ca http://www.muug.mb.ca/mailman/listinfo/roundtable
I believe the IP address is for information purposes only. It's cached when the record is originally setup and rarely if ever refreshed. This does not cause any problems as "whois" lookups have nothing to do with the DNS resolution process. John
participants (4)
-
Adam Thompson -
Bill Reid -
John Lange -
Sean Cody