Search Again: Re: Resolving Multiple Domains From: Men & Mice Support Date: Thursday, February 17, 2000 Time: 2:49:00 am 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

Messages In This Thread: Resolving Multiple Domains by Jim Ludwig on Feb 17, 2000 at 2:30:00 am Re: Resolving Multiple Domains by Men & Mice Support on Feb 17, 2000 at 2:49:00 am Re: Resolving Multiple Domains by Jim Ludwig on Feb 17, 2000 at 5:53:00 pm Re: Resolving Multiple Domains by Men & Mice Support on Feb 17, 2000 at 9:17:00 pm Re: Resolving Multiple Domains by Jim Ludwig on Feb 17, 2000 at 9:29:00 pm Re: Resolving Multiple Domains by Men & Mice Support on Feb 17, 2000 at 10:05:00 pm