This is just kind of a refresher, since the post was made at the
beginning of the month. The replies I am referencing are posted below
the "===" divider.

I just haven't gotten this to work. Comments below:

[Steve's response to my post]
The way you should perform this is as follows. The ISPs server have
it's own DNS name pointing to its IP address. You need to find out
from the ISP what the servers real DNS name is, and in your customers
internal DNS, create a CNAME record - not an A record as you normally
would. In a CNAME record you enter the ISPs dns name & not an IP
address.

[My response]
The real name is www.theirdomain.com so ... I guess I don't follow.
We have a Netware 6.0 server that uses the DNS suffix of
theirdomain.com so when we want to ping www.theirdomain.com it thinks
it should be resolving this internally because of the DNS suffix.

I did create a CNAME record and called the CNAME "www" because the
rest of it automatically is assigned to the real domain name in DNS.
Then I put "www.theirdomain.com where it says "Domain Name of Aliased
Host"

I restart everything and then when I ping www.theirdomain.com I get a
full screen of entries on the NAMED screen that says
"www.theirdomain.com is a CNAME for www.theirdomain.com, restarting
query". It never works.

If I don't add the "www" to the "Domain Name of Aliased Host" and just
add the domain name instead, it simply pings (successfully) the DNS
server itself.


[Steve's response to my post]
The CNAME record relays the request to from www.customer.com to
webserver.isp.com and the client will allways get the correct IP
address as long as the ISP does not change his DNS name.

[My response]
This is what I don't understand. How can it relay the request from
the Internal DNS server to an external one? My understanding was that
if the query was sent to a name that had your primary DNS suffix, it
would never leave the internal DNS server query. It won't contact
ROOT servers or forwarders.

If adding a CNAME allows that functionality then it still isn't
working for me. All the clients use a single internal DNS server in
their DHCP-assigned addresses. The server itself has 1 internal and 2
external from the ISP in the resolv.cfg file (for forwarders).

The "www" server exists outside my network on the outside world but I
can't ping it or browse to the web page because of the error on the
NAMED screen.

Any other help you guys can offer, I'd really appreciate it. I'd love
to get this working.


[Old posts to reference]
==============================
Hi Brian,

The way you should perform this is as follows. The ISPs server have
it's own DNS name pointing to its IP address. You need to find out
from the ISP what the servers real DNS name is, and in your customers
internal DNS, create a CNAME record - not an A record as you normally
would. In a CNAME record you enter the ISPs dns name & not an IP
address.

The CNAME record relays the request to from www.customer.com to
webserver.isp.com and the client will allways get the correct IP
address as long as the ISP does not change his DNS name.

Cheers,

Steve


On Fri, 06 May 2005 16:24:44 GMT, Brian Binder <bbinder@icswi.com>
wrote:

>This will probably be an easy one (hopefully!) for you guys. I've
>never had to deal with something like this so I'm going to ask in the
>forums.
>
>Easiest way for me to make this example would be as follows:
>
>[a] Our customer owns abc.com.
>[b] He does not host an internal web server, so another company hosts
>it for him, which we will be changing - just not yet.
>
>[c] Sometimes the www. address on the other end (ISP hosting it)
>changes.
>
>This causes them to not be able to contact their www server anymore.
>I think I can do something with a PTR to help this process can't I?
>Right now, I was using a DNS A record to point it at the right
>external address, but this is a pain when it changes, as I have to
>manually update it.
>
>www. doesn't resolve to anything internal, and they use internal DNS.
>So if they cannot resolve it internally, my understanding (same as MS
>DNS) is that it won't query Root servers or anything because you are
>trying to resolve a name that exists on the same domain that DNS is
>setup on.
>
>I'm just curious if there's a way to make a record that will somehow
>grab the external IP and make the update in DNS somehow.
>
>Thanks for any help!