Resolving Multiple Domains

Re: Resolving Multiple Domains

From:

Date:

Time:

Okay,
My IP addresses are: 209.183.206.219/218 only. I can order more if needed,
(for added cost) but just those 2 for now.

I will remove the 205.183.209.in-addr.arpa file.

On the PTR records question, I was looking at them and noticed that one of
them, (I'm not looking at present) had 2 different PTR records.

Once again, thank you very much for the help!

Jim Ludwig

> From: Men & Mice Support <cbuxton@menandmice.com>
> Reply-To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Date: Thu, 17 Feb 2000 13:17:52 -0800
> To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Subject: Re: Resolving Multiple Domains
>
> At 12:53 PM -0500 2/17/2000, Jim Ludwig wrote:
>> Chris,
>> Thank you for pointing out the error of my ways! I knew things were screwy,
>> but I am not, (if you hadn't already guessed) a DNS guru. I went through
>> and made a gob of changes to my DNS records, adding the . at the end of the
>> records. I just didn't know that I was supposed to do that! chcnova.com is
>> actually one of my clients, but I use the Domain Assistant and must've
>> forgotten to uncheck, 'create reverse records auto-magically'.
>>
>> I do know that what I have is VERY ugly, and that was the reason I wanted to
>> clean it up. I am not in the habit of letting things get so weird, but we
>> have a 9 month old and he has pulled all of my time away from being a
>> computer geek ;-). If you would, could you tell me what I should have my
>> ISP do to make the records match and be correct?
>
> To do that, I'd need to know what range of IP addresses you have,
> preferably using subnet notation (as in 209.183.206.216/29). Because
> in reality, the method your ISP decided to try to use really doesn't
> work well.
>
>> I was looking through my zone files and found that there are several PTR
>> records in my reverse domain files. Should those be there?
>
> I don't understand the question. Your reverse zone files should have
> PTR records and NS records, with nothing else. You shouldn't have
> multiple PTR records for any given IP address.
>
>> Also, I have a
>> zone file that reads:
>>
>> 205.183.209.in-addr.arpa
>>
>> What is that?
>
> That's one of those reverse zone files automatically created by the
> Domain Assistant, because you created an A record for
> dns1.atlantech.net.chcnova.com.
>
> Remove this file.
>
>> Thanks for ALL of the help! You guys are great!
>>
>> Jim Ludwig
>>
>>
>>
>>> From: Men & Mice Support <cbuxton@menandmice.com>
>>> Reply-To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
>>> Date: Wed, 16 Feb 2000 18:49:02 -0800
>>> To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
>>> Subject: Re: Resolving Multiple Domains
>>>
>>> At 9:30 PM -0500 2/16/2000, Jim Ludwig wrote:
>>>> Folks,
>>>>
>>>> I have a small web hosting business running on Macs. I use
>>>> QuickDNS and DNS
>>>> Expert and love both. My question is actually more along the lines of how
>>>> to. Here it is. I have multiple DNS entries pointing at only 2 different
>>>> IP addresses. When I pull up EIMS, it does a reverse lookup and tells me
>>>> that the found name is one of the other domain names that I host.
>>>> Everything still seems to work, but it bothers me that I can't seem to
>>>> figure out how to create new zones properly. They work, but they aren't
>>>> pretty. I hope this doesn't just seem like rambling and that someone has
>>>> some ideas.
>>>
>>> Hi Jim,
>>>
>>> Your reverse record for 209.183.206.219, frankly, looks pretty messy.
>>>
>>> The class C subnet is delegated to your ISP directly from the root
>>> servers, as follows:
>>> 206.183.209.in-addr.arpa. NS dns1.atlantech.net.
>>> 206.183.209.in-addr.arpa. NS dns2.atlantech.net.
>>>
>>> After that, things get muddy. Here's what dns1.atlantech.net says:
>>> 206.183.209.in-addr.arpa. NS host2.atlantech.net.
>>> 206.183.209.in-addr.arpa. NS host3.atlantech.net.
>>> 219.206.183.209.in-addr.arpa. NS dns.interrupt9.com.
>>> 219.206.183.209.in-addr.arpa. PTR dns.interrupt9.com.chcnova.com.
>>>
>>> Those last two records look really screwy. The third record is an
>>> unrecommended way to delegate an individual IP address - it's a
>>> method mentioned in RFC 2317 as something that generally shouldn't be
>>> done.
>>>
>>> The fourth record, though, is just plain wrong-looking.
>>>
>>> I queried your server (as indicated by the NS record), and it said:
>>> 219.206.183.209.in-addr.arpa. PTR dns.interrupt9.com.chcnova.com.
>>> 206.183.209.in-addr.arpa. NS dns.interrupt9.com.chcnova.com.
>>> 206.183.209.in-addr.arpa. NS dns1.atlantech.net.chcnova.com.
>>> dns.interrupt9.com.chcnova.com. A 209.183.206.219
>>> dns1.atlantech.net.chcnova.com. A 209.183.205.35
>>>
>>> So dns1.atlantech.net doesn't agree with your server. This means that
>>> they didn't even implement the unrecommended procedure correctly.
>>> Very bad.
>>>
>>> Furthermore, all your names end in chcnova.com - ???
>>>
>>> I queried your server for chcnova.com, and got this:
>>> chcnova.com. NS dns.interrupt9.com.chcnova.com.
>>> chcnova.com. NS dns1.atlantech.net.chcnova.com.
>>>
>>> Put a period on the end, after "dns.interrupt9.com", to get rid of
>>> the extra "chcnova.com.". Same with "dns1.atlantech.net.".
>>>
>>> Then edit your version of the reverse zone. Then tell your ISP to fix
>>> their version of the reverse zone - remove the PTR record. Or, they
>>> can reread RFC 2317 and use the procedure recommended there, which
>>> would involve a few minor changes to their records and yours.
>>>
>>> Lastly: Change the PTR record to report the name you want EIMS to use.
>>>
>>> BTW: As you said, what you have works. It's pretty ugly, but it
>>> works. If you don't feel the need to fix it, everything will continue
>>> to work.
>>> ____________________________________________________________________
>>> Chris Buxton cbuxton@menandmice.com
>>> Men & Mice http://www.menandmice.com
>>> Makers of: QuickDNS Pro

Sales:
888/4-DPOINT

Support:
858/452-3696