Ben at BC Web wrote:
> We had an arrangement with our backend ISP where they provide us with
> secondary DNS service. We switched backend ISPs, and so we made new
> arrangements for a secondary DNS. The problem is that in testing this new
> arrangement, we're getting a strange error message.
>
> Our own address pool is 66.224.41.x, and our new secondary DNS server is
> 204.250.116.119. I believe they set this up as a secondary IP on that
> server (it also holds either .17 or .18 as its primary IP) so that they
> would have the option of later splitting the IPs (running one DNS server on
> .18 and one on .19). We created an A record in our zone that points to this
> new secondary DNS server. So the A record is for dns2.bcwebhost.net
> pointing to 204.250.116.119.
A whois on Domain Name: BCWEBHOST.NET comes up with
Domain servers in listed order:
NS1.BOSSIG.COM 208.26.176.226
BCW4.BCWEBHOST.NET 66.224.41.3
I don't see dns2.bcwebhost.net or 204.250.116.119 there at all. When
did you submit the update to VeriSign? Until the .net zone has been
updated with your new servers no one is going to get the right answers.
Note also that that a lookup on 119.116.250.204.in-addr.arpa. fails. You
should ask Advanced Telcom Group to either delegate to you or put entries
in their tables.
--
[EMAIL PROTECTED]
"Hangers on though you be friends be more humble
when asking for seconds."
Katsuhito Masaki (Grandfather); Tenchi Muyo Episode 7
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Please visit the Knowledge Base for answers to frequently asked
questions: http://www.ipswitch.com/support/IMail/
