JonEast
01-21-2001, 02:37 PM
I am building a site for someone who had registered their domain (mercenaryfilms.co.uk) with register.com (http://www.register.com).
I initially hosted it with Digitalspace (http://www.digitalspace.net), but there were various problems, so I moved to FutureQuest for reliability reasons.
While hosting with Digitalspace:
Using the register.com account, I initially changed the 'A' record to point to the IP address of the website to test it.[nbsp][nbsp]After propagation, this worked.[nbsp][nbsp]Later, I used their 'Modify DNS' option to change the nameservers to Digitalspace's.[nbsp][nbsp]DNS resolution continued to work.
Then I cancelled the Digitalspace hosting account, telling them that I was moving to FutureQuest, and asking them whether there was anything else I needed to do to facilitate this.[nbsp][nbsp]They cancelled the hosting about a week ago.
Now I am with FutureQuest, I can't figure out how to get DNS resolution to work for the new hosting!
register.com says:
that my site is on someone else's nameservers (presumably Digitalspace's, right?) and that they can't do anything.
The 'Modify DNS' option no longer appears in register.com's account manager, which seems consistent with this.
However, dig says:
01/21/01 17:32:50 dig mercenaryfilms.co.uk @ dns23.register.com
Dig mercenaryfilms.co.uk@dns24.register.com (209.67.50.88) ...
failed, couldn't connect to nameserver
Dig mercenaryfilms.co.uk@dns23.register.com (209.67.50.87) ...
Authoritative Answer
[nbsp]Query for mercenaryfilms.co.uk type=255 class=1
[nbsp][nbsp]mercenaryfilms.co.uk NS (Nameserver) dns23.register.com
[nbsp][nbsp]mercenaryfilms.co.uk NS (Nameserver) dns24.register.com
[nbsp][nbsp]mercenaryfilms.co.uk SOA (Zone of Authority)
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]Primary NS: dns23.register.com
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]Responsible person: root@register.com
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]serial:200007275
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]refresh:10800s (3 hours)
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]retry:3600s (60 minutes)
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]expire:604800s (7 days)
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]minimum-ttl:86400s (24 hours)
[nbsp][nbsp]mercenaryfilms.co.uk A (Address) 216.222.193.134
[nbsp][nbsp]mercenaryfilms.co.uk MX (Mail Exchanger) Priority: 10 mxmail.register.com
[nbsp][nbsp]mercenaryfilms.co.uk NS (Nameserver) dns23.register.com
[nbsp][nbsp]mercenaryfilms.co.uk NS (Nameserver) dns24.register.com
(Doesn't that mean that register.com's nameservers are authoritative?)
Could anyone help me?
I'm not sure who to ask, or what to ask them, in order to establish whose nameservers are really 'authoritative for the domain' mercenaryfilms.co.uk - nor can I figure out what I need do to clear up this mess!
Hopefully yours,
Jon East
I initially hosted it with Digitalspace (http://www.digitalspace.net), but there were various problems, so I moved to FutureQuest for reliability reasons.
While hosting with Digitalspace:
Using the register.com account, I initially changed the 'A' record to point to the IP address of the website to test it.[nbsp][nbsp]After propagation, this worked.[nbsp][nbsp]Later, I used their 'Modify DNS' option to change the nameservers to Digitalspace's.[nbsp][nbsp]DNS resolution continued to work.
Then I cancelled the Digitalspace hosting account, telling them that I was moving to FutureQuest, and asking them whether there was anything else I needed to do to facilitate this.[nbsp][nbsp]They cancelled the hosting about a week ago.
Now I am with FutureQuest, I can't figure out how to get DNS resolution to work for the new hosting!
register.com says:
that my site is on someone else's nameservers (presumably Digitalspace's, right?) and that they can't do anything.
The 'Modify DNS' option no longer appears in register.com's account manager, which seems consistent with this.
However, dig says:
01/21/01 17:32:50 dig mercenaryfilms.co.uk @ dns23.register.com
Dig mercenaryfilms.co.uk@dns24.register.com (209.67.50.88) ...
failed, couldn't connect to nameserver
Dig mercenaryfilms.co.uk@dns23.register.com (209.67.50.87) ...
Authoritative Answer
[nbsp]Query for mercenaryfilms.co.uk type=255 class=1
[nbsp][nbsp]mercenaryfilms.co.uk NS (Nameserver) dns23.register.com
[nbsp][nbsp]mercenaryfilms.co.uk NS (Nameserver) dns24.register.com
[nbsp][nbsp]mercenaryfilms.co.uk SOA (Zone of Authority)
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]Primary NS: dns23.register.com
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]Responsible person: root@register.com
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]serial:200007275
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]refresh:10800s (3 hours)
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]retry:3600s (60 minutes)
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]expire:604800s (7 days)
[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]minimum-ttl:86400s (24 hours)
[nbsp][nbsp]mercenaryfilms.co.uk A (Address) 216.222.193.134
[nbsp][nbsp]mercenaryfilms.co.uk MX (Mail Exchanger) Priority: 10 mxmail.register.com
[nbsp][nbsp]mercenaryfilms.co.uk NS (Nameserver) dns23.register.com
[nbsp][nbsp]mercenaryfilms.co.uk NS (Nameserver) dns24.register.com
(Doesn't that mean that register.com's nameservers are authoritative?)
Could anyone help me?
I'm not sure who to ask, or what to ask them, in order to establish whose nameservers are really 'authoritative for the domain' mercenaryfilms.co.uk - nor can I figure out what I need do to clear up this mess!
Hopefully yours,
Jon East