Search Again:

Re: Host Records?

From: John May
Date: Sunday, December 19, 2004
Time: 6:03:28 pm

Cool, found it all now. Thanks Chris - you rule!

- John


>At 9:25 AM -0500 12/19/04, John May wrote:
>>>We're working on transferring our pointinspace.com domain, which
>>>has our ns1. and ns2.pointinspace.com DNS servers tied to it, off
>>>of Network Solutions.
>>>
>>>It used to be required to make (and keep up to date) Host records
>>>at Network Solutions for nameservers specifying their IP
>>>addresses. Does this not exist anymore? I couldn't find any info
>>>on their site...
>>>
>>>Thanks for any help!
>>>
>>> - John
>>
>>
>>I'm still confused a bit about this. It used to be that Network
>>Solutions registered the IP addresses of the nameservers for the
>>domain. However, I can't find that setting anywhere anymore, nor
>>with any other registrar.
>
>That's because they make it hard to find. For some registrars, you
>actually have to call them, speak to a live human, and hope that
>human understands the request.
>
>>It seems there's a catch 22 here. InterNic stores what name
>>servers are responsible for a domain in their root server.
>>However, if those nameservers are sub-domains of the domain that
>>they're nameservers for, how does that work?
>
>The solution is called a "glue" record. It's an A record that would
>otherwise be out of place. In this case, it's an A record for the
>name server in the com zone; it should exactly match the A record in
>your zone.
>
>If I query one of the servers authoritative for com about your
>domain, it gives me this answer:
>
>$ dig pointinspace.com @f.gtld-servers.net +norecurse
>
>;; AUTHORITY SECTION:
>pointinspace.com. 172800 IN NS ns1.pointinspace.com.
>pointinspace.com. 172800 IN NS ns2.pointinspace.com.
>
>;; ADDITIONAL SECTION:
>ns1.pointinspace.com. 172800 IN A 66.151.191.68
>ns2.pointinspace.com. 172800 IN A 66.151.191.77
>
>It gets all four records from the com zone, not from your servers.
>
>>I assume that's what the old method of registering their IPs with
>>Network Solutions was for?
>
>Yes.
>
>>Is it handled differently now?
>
>No.
>
>>Basically, our nameservers are ns1.pointinspace.com and
>>ns2.pointinspace.com. Our domain is pointinspace.com, and our
>>registrant record (with enom.com now) says ns1/ns2 are the DNS
>>servers for it.
>
>Then you have to change your host records with enom.com, not with NetSol.
>
>>I'm concerned here as we need to do an IP reallocation, involving
>>changing the IPs of ns1/ns2. So the big question is, do I need to
>>change the IP settings for the nameservers anywhere else than in
>>our local host record for the pointinspace.com domain?
>
>Yes, definitely. If you go to enom.com and click on "my enom",
>there's probably some way to change your name server records. At
>least, that's what it sounds like from their help page.
>
>Chris Buxton
>Men & Mice - Making DNS Easy


--

-------------------------------------------------------------------
John May : President <http://www.pointinspace.com>
Point In Space Internet Solutions jmay@pointinspace.com

Professional Lasso / PHP / MySQL / FileMaker Pro Hosting




Messages In This Thread:



Return to Digital Point Solutions' Home Page