 |  |
>I had to move my servers to a new colo host last week. In advance of the
Re: Really Fouled Up
From: Men & Mice Support
Date: Friday, July 16, 1999
Time: 7:18:00 pm
>move, I was assigned:
>
>>Your IP pool is
>>209.75.187.201-206 with a gateway of 209.75.187.200 and a netmask of
>>255.255.255.248 and your broadcast will be 209.75.187.207
>
>Being no subnetting wizard, I took them at their word and started assigning
>these new numbers and creating new QDNS data files that I could simply copy
>into the Primary Data folder when the time came, etc. I sent my new host a
>list of how I wanted the reverse resolution set up.
>
>I assigned the .201 address and sent in domain registrations to InterNIC
>using the .201 address -- which turned out to be the gateway address for
>this subnet. The result was that the .201 address ended up listed with
>INterNIC as the primary name server web and mail server address for umpteen
>domains. I've been trying to straighten it out ever since.
The simplest solution would have been to give the gateway a different
address. Once something's registered with Internic, it is best to leave it
that way if at all possible.
The two things you can't change are the network number (200) and the
broadcast address (207). (Well, technically, you *can* change the broadcast
address, but not with Mac or Windows.) The gateway address is just the
address you assign to your router - it can be any legal address on your
subnet.
>Of course, this made my mail server unreachable so I could not send
>corrected templates in to InterNIC. After multiple phone calls, I finally
>had to fax instructions to InterNIC (including a scan of a photo ID!). And
>they still haven't straightened out the mess -- they did not follow the
>instructions I sent.
Network Solutions (aka Internic) isn't exactly responsive in cases like
this. Which is why we want competition.
>And though my upstream says they have the reverse DNS working, I can't get
>the numbers to resolve.
>
>Can any of you resolve the following numbers?
>
>209.75.187.202
> .203
> .205
> .206
No. Who's your upstream? If the answer is ni.net, then they haven't
implemented your reverse records yet. If the answer is not ni.net, then
your upstream is going to have some explaining to do, as ni.net is
responsible for your reverse records.
Here are the delegation records for the class C subnet surrounding your block:
187.75.209.in-addr.arpa. NS ns1.ni.net.
187.75.209.in-addr.arpa. NS ns2.ni.net.
These servers have no matching zone file, though.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com http://www.menandmice.com
Messages In This Thread:
Return to Digital Point Solutions' Home Page