MUUG Meeting, Dec 14, 7:30pm -- Round-table, Mingling & Munchies
The Manitoba UNIX User Group (MUUG) will be holding its next monthly meeting on Tuesday, December 14. The meeting topic for this month is as follows: Round-table, Mingling & Munchies As the holiday hustle and bustle gets into high gear, we'll take it easy this month, with a longer-than-usual round-table session (if there's a need for it), followed by a time for mingling and nibbling on munchies (instead of the usual, short coffee break). There will also be a door-prize draw at the end, but in order to enter the draw this month, we ask that you bring a tin or other non-perishable food item for Winnipeg Harvest. You'll get one draw ticket per item you bring, to a maximum of 3 tickets. So, please be generous, and you might just take home a cool book from O'Reilly! The group holds its general meetings at 7:30pm on the second Tuesday of every month from September to June. (There are no meetings in July and August.) Meetings are open to the general public; you don't have to be a MUUG member to attend. ********************************************************************** Please note our meeting location: The IBM offices, at 400 Ellice Ave. (between Edmonton and Kennedy). When you arrive, you will have to sign in at the reception desk, and then wait for someone to take you (in groups) to the meeting room. Please try to arrive by about 7:15pm, so the meeting can start promptly at 7:30pm. Don't be late, or you may not get in. (But don't come too early either, since security may not be there to let you in before 7:15 or so.) Non-members may be required to show photo ID at the security desk. Limited parking is available for free on the street, either on Ellice Ave. or on some of the intersecting streets. Indoor parking is also available nearby, at Portage Place, for $5.00 for the evening. Bicycle parking is available in a bike rack under video surveillance located behind the building on Webb Place. ********************************************************************** For more information about MUUG, and its monthly meetings, check out their Web server: http://www.muug.mb.ca/ Help us promote this month's meeting, by putting this poster up on your workplace bulletin board or other suitable public message board: http://www.muug.mb.ca/meetings/MUUGmeeting.pdf -- Gilbert E. Detillieux E-mail: <gedetil@muug.mb.ca> Manitoba UNIX User Group Web: http://www.muug.mb.ca/ PO Box 130 St-Boniface Phone: (204)474-8161 Winnipeg MB CANADA R2H 3B4 Fax: (204)474-7609
I've had to move my server and therefore my IPs of my NS records change too. Since doing that I've not been able to get the whois records of the domains to show properly (or with the right IPs). It seems that whatever application sets the DNS servers in the whois records 'remembers' the hostname:ip pairs _forever_ or some undocumented period of time. I have 3 NS servers. Two of them are new (geographic disparity FTW). The old server's IP has changed and I can't get it to show up properly in _ANY_ CIRA whois record. Example: tfh.ca Whois shows up with DNS1 hostname empty and DNS2 with an old IP and DNS3 is correct. I have been able to get it working again by choosing new names for the NS records (BOOOO!) such as using '{nsa,nsb,nsc}.$domain' instead of my preferred '{a,b,c}.ns.$domain. In all of these cases the NS records for the domain show perfectly fine but I've got a few folks (myself included) that get a bit pedantic about the whois record matching the root NS records. Does anyone know why CIRA seems to cache these NS resolution records indefinitely? The TTL on the domains are 600 seconds so either there is a policy which ignores them or there is a rule I don't know about. (Tried for weeks to get this to work so I'm sure I've gotten past the 1 week rule). I'm sure it is CIRA because this behavior persists between two different registrars and one '.com' doesn't show it... so it's localized to .ca's. Any ideas? -- Sean (mobile)
That certainly sounds strange. I have done this in the past and it worked. They have cutover to new registry software a couple of months ago so it is possible this is a bug. Have you contacted CIRA directly? On 08/12/10 09:57, Sean Cody wrote:
I've had to move my server and therefore my IPs of my NS records change too.
Since doing that I've not been able to get the whois records of the domains to show properly (or with the right IPs). It seems that whatever application sets the DNS servers in the whois records 'remembers' the hostname:ip pairs _forever_ or some undocumented period of time.
I have 3 NS servers. Two of them are new (geographic disparity FTW). The old server's IP has changed and I can't get it to show up properly in _ANY_ CIRA whois record.
Example: tfh.ca
Whois shows up with DNS1 hostname empty and DNS2 with an old IP and DNS3 is correct.
I have been able to get it working again by choosing new names for the NS records (BOOOO!) such as using '{nsa,nsb,nsc}.$domain' instead of my preferred '{a,b,c}.ns.$domain.
In all of these cases the NS records for the domain show perfectly fine but I've got a few folks (myself included) that get a bit pedantic about the whois record matching the root NS records.
Does anyone know why CIRA seems to cache these NS resolution records indefinitely? The TTL on the domains are 600 seconds so either there is a policy which ignores them or there is a rule I don't know about. (Tried for weeks to get this to work so I'm sure I've gotten past the 1 week rule).
I'm sure it is CIRA because this behavior persists between two different registrars and one '.com' doesn't show it... so it's localized to .ca's.
Any ideas?
I'm not sure I'm understanding your situation completely, but if you have a name server in the same domain, you can't just edit the zone. You have to change the name servers at the registrar. The registrar then pushes it up to CIRA which pushes this down to it's name servers. On the other hand, if you are just talking about the IPs that are displayed in a 'whois' lookup, I don't believe those are not significant. They are typically cached when the name server records are created and are informational only. Actual DNS resolution relies on resolving the name server by name in real-time, not the IP is in the whois record. -- John Lange www.johnlange.ca
I've not contacted the directly as it seems most questions solutions are 'talk to your registrar' (who for this problem is just shoulder shrugging). -- Sean (mobile) On 2010-12-08, at 12:50 PM, Bill Reid <billreid@shaw.ca> wrote:
That certainly sounds strange. I have done this in the past and it worked. They have cutover to new registry software a couple of months ago so it is possible this is a bug. Have you contacted CIRA directly?
On 08/12/10 09:57, Sean Cody wrote:
I've had to move my server and therefore my IPs of my NS records change too.
Since doing that I've not been able to get the whois records of the domains to show properly (or with the right IPs). It seems that whatever application sets the DNS servers in the whois records 'remembers' the hostname:ip pairs _forever_ or some undocumented period of time.
I have 3 NS servers. Two of them are new (geographic disparity FTW). The old server's IP has changed and I can't get it to show up properly in _ANY_ CIRA whois record.
Example: tfh.ca
Whois shows up with DNS1 hostname empty and DNS2 with an old IP and DNS3 is correct.
I have been able to get it working again by choosing new names for the NS records (BOOOO!) such as using '{nsa,nsb,nsc}.$domain' instead of my preferred '{a,b,c}.ns.$domain.
In all of these cases the NS records for the domain show perfectly fine but I've got a few folks (myself included) that get a bit pedantic about the whois record matching the root NS records.
Does anyone know why CIRA seems to cache these NS resolution records indefinitely? The TTL on the domains are 600 seconds so either there is a policy which ignores them or there is a rule I don't know about. (Tried for weeks to get this to work so I'm sure I've gotten past the 1 week rule).
I'm sure it is CIRA because this behavior persists between two different registrars and one '.com' doesn't show it... so it's localized to .ca's.
Any ideas?
_______________________________________________ Roundtable mailing list Roundtable@muug.mb.ca http://www.muug.mb.ca/mailman/listinfo/roundtable
On 2010-12-08 Sean Cody wrote:
Example: tfh.ca
Whois shows up with DNS1 hostname empty and DNS2 with an old IP and DNS3 is correct.
Hmm, very strange. Shouldn't those entries in the "Name servers:" section just come from the NS settings you setup with your registrar? If you setup new NS entries with your registrar, do you just enter IP's (no hostnames)? If so, then the reverse-DNS should dictate what hostname shows up in the whois. I (my company) is a OpenSRS/Tucows reseller so if you get really stuck I could go to bat for you to get this solved if you wanted to xfer your domain to me as the registrar/reseller. I know OpenSRS is very good about these sorts of things. In my experience with their interface it's simply a matter of punching in new IPs for your NS's (and deleting old ones). Very strange, but my whois appears to lack IP's completely (just hostnames)!! But John is right, the whois doesn't really matter to anyone, right?
participants (5)
-
Bill Reid -
gedetil＠cs.umanitoba.ca -
John Lange -
Sean Cody -
Trevor Cordes